Triple
T24991094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutlej River at Karcham |
E625449
|
entity |
| Predicate | confluenceLocatedAt |
P11842
|
FINISHED |
| Object | Karcham |
—
|
NE NERFINISHED |
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: Karcham | Statement: [Sutlej River at Karcham, confluenceLocatedAt, Karcham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confluenceLocatedAt Context triple: [Sutlej River at Karcham, confluenceLocatedAt, Karcham]
-
A.
confluenceLocation
Indicates the place where two or more flowing entities (such as rivers or streams) meet and merge.
-
B.
locatedAtConfluenceOf
chosen
Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
-
C.
isConfluenceAtCity
Indicates that the confluence (meeting point) of two or more water bodies occurs at or within the specified city.
-
D.
confluenceWith
Indicates that one entity joins or merges together with another, typically at a shared meeting point.
-
E.
confluenceDistrict
Indicates a relationship where an area or region is designated as the district surrounding or encompassing the confluence of two or more water bodies.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44a457a888190beb43ff433b12abb |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:03 a.m.