Triple
T28028151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bazarak |
E708184
|
entity |
| Predicate | distanceToKabul_km |
P62305
|
FINISHED |
| Object | approximately 150 |
—
|
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 150 | Statement: [Bazarak, distanceToKabul_km, approximately 150]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKabul_km Context triple: [Bazarak, distanceToKabul_km, approximately 150]
-
A.
distanceToKabul
chosen
Indicates the measured spatial distance between a given location or entity and the city of Kabul.
-
B.
distanceFromSamarkand_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Samarkand.
-
C.
distanceFromLashkarGah
Indicates the measured distance between a given location and the city of Lashkar Gah.
-
D.
distanceToKhiva
Indicates the spatial distance between a given location or object and the city of Khiva.
-
E.
distanceToKandaharApproxKm
Indicates an approximate physical distance, measured in kilometers, between a given entity and the location of Kandahar.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: April 27, 2026, 8:14 p.m.