Triple
T3668526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guddu Barrage |
E77819
|
entity |
| Predicate | connectsTransportRoute |
P3034
|
FINISHED |
| Object | road across Indus River at Guddu |
—
|
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: road across Indus River at Guddu | Statement: [Guddu Barrage, connectsTransportRoute, road across Indus River at Guddu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsTransportRoute Context triple: [Guddu Barrage, connectsTransportRoute, road across Indus River at Guddu]
-
A.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
B.
transportConnectionTo
Indicates a relationship where one entity provides or participates in a means of transportation that connects or leads to another entity.
-
C.
transportCorridor
chosen
Indicates a route or pathway used to move people, goods, or resources between locations.
-
D.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
E.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42997d88190bc765559bd7645fc |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.