Triple
T8573292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karaj |
E202981
|
entity |
| Predicate | distanceFromTehran_km |
P44352
|
FINISHED |
| Object | approximately 20–40 |
—
|
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 20–40 | Statement: [Karaj, distanceFromTehran_km, approximately 20–40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTehran_km Context triple: [Karaj, distanceFromTehran_km, approximately 20–40]
-
A.
distanceFromTehran
chosen
Indicates the spatial distance between a given entity and the city of Tehran.
-
B.
distanceFromSamarkand_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Samarkand.
-
C.
distanceToPersepolis
Indicates the measured spatial distance between a given entity and the location of Persepolis.
-
D.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
E.
distanceToKabul
Indicates the measured spatial distance between a given location or entity and the city of Kabul.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea458c1081908e79bee2cbf97207 |
completed | March 31, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.