Triple
T23646782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazerun |
E584057
|
entity |
| Predicate | distanceToShiraz |
P153020
|
FINISHED |
| Object | approximately 145 km west |
—
|
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 145 km west | Statement: [Kazerun, distanceToShiraz, approximately 145 km west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToShiraz Context triple: [Kazerun, distanceToShiraz, approximately 145 km west]
-
A.
distanceFromTehran
Indicates the spatial distance between a given entity and the city of Tehran.
-
B.
distanceToPersepolis
Indicates the measured spatial distance between a given entity and the location of Persepolis.
-
C.
distanceFromSamarkand_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Samarkand.
-
D.
distanceFromQom
Indicates the spatial distance between an entity and the location Qom.
-
E.
distanceToKhiva
Indicates the spatial distance between a given location or object and the city of Khiva.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b28571bc8190b3f7275068d19320 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:48 p.m.