Triple
T5237043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalalabad |
E118245
|
entity |
| Predicate | distanceToKabul |
P62305
|
FINISHED |
| Object | approximately 150 km east of Kabul |
—
|
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 km east of Kabul | Statement: [Jalalabad, distanceToKabul, approximately 150 km east of Kabul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKabul Context triple: [Jalalabad, distanceToKabul, approximately 150 km east of Kabul]
-
A.
distanceFromSamarkand_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Samarkand.
-
B.
distanceFrom Peshawar
Indicates the spatial distance between a given location or entity and the city of Peshawar.
-
C.
distanceFromAshgabat
Indicates the measured spatial distance between a given location and the city of Ashgabat.
-
D.
distanceFromAlmaty_km
Indicates the distance, measured in kilometers, between a given place or object and the city of Almaty.
-
E.
distanceToLahore_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Lahore.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b2595c88190b4ca0b99c2f31472 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79e9d794819097bb628c603d14af |
completed | March 20, 2026, 4:46 p.m. |
Created at: March 20, 2026, 1:49 p.m.