Triple
T9813515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zanjan |
E238337
|
entity |
| Predicate | distanceToTehran |
P44352
|
FINISHED |
| Object | approximately 300 km |
—
|
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 300 km | Statement: [Zanjan, distanceToTehran, approximately 300 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTehran Context triple: [Zanjan, distanceToTehran, approximately 300 km]
-
A.
distanceFromTehran
chosen
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.
distanceToKabul
Indicates the measured spatial distance between a given location or entity and the city of Kabul.
-
E.
distanceFromBaghdad
Indicates the spatial distance between a given location or entity and the city of Baghdad.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb22410208190b82b81a4df800f80 |
completed | April 2, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:30 p.m.