Triple
T31462868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karun-3 Dam |
E802649
|
entity |
| Predicate | downstreamStructure |
P137350
|
FINISHED |
| Object | Karun-1 Dam |
—
|
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: Karun-1 Dam | Statement: [Karun-3 Dam, downstreamStructure, Karun-1 Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: downstreamStructure Context triple: [Karun-3 Dam, downstreamStructure, Karun-1 Dam]
-
A.
downstreamFrom
Indicates that one entity is located or occurs at a point further along the natural flow or direction of another entity, typically in a linear or directional system such as a river, pipeline, or process sequence.
-
B.
downstreamFacility
chosen
Indicates that one facility is located or operates downstream from another facility within a flow or process network.
-
C.
downstreamBoundary
Indicates that one entity serves as the downstream limit or endpoint of another entity’s flow, process, or influence.
-
D.
downstreamProcess
Indicates that one process occurs later in a sequence and depends on the outputs or results of another, preceding process.
-
E.
downstreamUse
Indicates that one entity makes use of the outputs, results, or products generated by another entity at a later stage in a process or workflow.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:21 p.m.