Triple
T13924393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirakud Dam |
E334824
|
entity |
| Predicate | lengthIncludingDykes |
P43546
|
FINISHED |
| Object | about 25.8 kilometres |
—
|
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: about 25.8 kilometres | Statement: [Hirakud Dam, lengthIncludingDykes, about 25.8 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthIncludingDykes Context triple: [Hirakud Dam, lengthIncludingDykes, about 25.8 kilometres]
-
A.
waterwayLengthKilometres
Indicates the total length of a waterway, measured in kilometres.
-
B.
damLength
chosen
Indicates the measured longitudinal extent of a dam from one end to the other.
-
C.
hasApproxLengthAlongRiver
Indicates that an entity has an approximate measured length that follows the course of a river rather than a straight-line distance.
-
D.
navigableLengthApproxKm
Indicates the approximate distance, measured in kilometers, over which something (typically a waterway) can be navigated.
-
E.
hasEmbankment
Indicates that one entity possesses or is characterized by an embankment, such as a raised structure built to contain, support, or protect against water or terrain.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa6cd9881908f652538f4613f37 |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.