Triple
T37970454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiratpur Sahib |
E947267
|
entity |
| Predicate | hasRiverBankSite |
P8340
|
FINISHED |
| Object | cremation ghat on the Sutlej River |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: cremation ghat on the Sutlej River | Statement: [Kiratpur Sahib, hasRiverBankSite, cremation ghat on the Sutlej River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverBankSite Context triple: [Kiratpur Sahib, hasRiverBankSite, cremation ghat on the Sutlej River]
-
A.
hasRiverBankSettlement
Indicates that a settlement is located on or directly adjacent to the bank of a river.
-
B.
primaryRiverBank
Indicates that a river segment is primarily associated with or bordered by a particular river bank (e.g., left or right bank) as its main adjoining side.
-
C.
hasParkAlongBank
Indicates that a park is located adjacent to or running alongside the bank of a water body.
-
D.
hasSacredRiverBank
Indicates that a place or entity possesses a riverbank regarded as sacred or holy.
-
E.
hasLandmarkOnBank
chosen
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:20 p.m.