Triple
T24261576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sangtuda 1 Dam |
E604717
|
entity |
| Predicate | distanceFromDushanbe |
P155365
|
FINISHED |
| Object | approximately 160 km southeast |
—
|
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 160 km southeast | Statement: [Sangtuda 1 Dam, distanceFromDushanbe, approximately 160 km southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDushanbe Context triple: [Sangtuda 1 Dam, distanceFromDushanbe, approximately 160 km southeast]
-
A.
distanceFromKigali
Indicates the measured spatial distance between a given location and the city of Kigali.
-
B.
distanceFromKathmandu
Indicates the measured spatial distance between a given location or entity and the city of Kathmandu.
-
C.
distanceFromSamarkand_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Samarkand.
-
D.
distanceToKabul
Indicates the measured spatial distance between a given location or entity and the city of Kabul.
-
E.
distanceFromAshgabat
Indicates the measured spatial distance between a given location and the city of Ashgabat.
- F. None of above. chosen
Provenance (4 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6727388190862e3ce09c372c70 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:06 a.m.