Triple
T26226164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jal Marg Vikas Project |
E655897
|
entity |
| Predicate | lengthOfWaterway_km |
P59548
|
FINISHED |
| Object | approximately 1390 |
—
|
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: approximately 1390 | Statement: [Jal Marg Vikas Project, lengthOfWaterway_km, approximately 1390]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthOfWaterway_km Context triple: [Jal Marg Vikas Project, lengthOfWaterway_km, approximately 1390]
-
A.
waterwayLengthKilometres
chosen
Indicates the total length of a waterway, measured in kilometres.
-
B.
riverLength
Indicates the measured extent of a river from its source to its mouth, typically expressed as a linear distance.
-
C.
riverLengthContext
Indicates the contextual or situational information under which a river’s length is measured or considered.
-
D.
waterwayWidth
Indicates the measured width of a waterway, typically the distance across it from one bank or edge to the opposite.
-
E.
navigableLengthApproxKm
Indicates the approximate distance, measured in kilometers, over which something (typically a waterway) can be navigated.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d53d94081909d0ae8f05e8de84c |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:58 p.m.