Triple
T25114966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spin Boldak |
E629101
|
entity |
| Predicate | distanceToKandaharApproxKm |
P175285
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [Spin Boldak, distanceToKandaharApproxKm, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKandaharApproxKm Context triple: [Spin Boldak, distanceToKandaharApproxKm, 100]
-
A.
distanceToKabul
Indicates the measured spatial distance between a given location or entity and the city of Kabul.
-
B.
distanceFromLashkarGah
Indicates the measured distance between a given location and the city of Lashkar Gah.
-
C.
distanceToKhiva
Indicates the spatial distance between a given location or object and the city of Khiva.
-
D.
distanceFrom Peshawar
Indicates the spatial distance between a given location or entity and the city of Peshawar.
-
E.
distanceFromSamarkand_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Samarkand.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 18, 2026, 6:27 a.m.