Triple
T28059469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavasan |
E709061
|
entity |
| Predicate | distanceFromTehranApprox |
P44352
|
FINISHED |
| Object | about 11–20 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: about 11–20 km | Statement: [Lavasan, distanceFromTehranApprox, about 11–20 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTehranApprox Context triple: [Lavasan, distanceFromTehranApprox, about 11–20 km]
-
A.
distanceFromTehran
chosen
Indicates the spatial distance between a given entity and the city of Tehran.
-
B.
distanceToShiraz
Indicates the spatial distance between a given entity and the location of Shiraz.
-
C.
distanceFromBaku
Indicates the measured distance between a given place or object and the city of Baku.
-
D.
distanceFromSamarkand_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Samarkand.
-
E.
directionFromTehran
Indicates the cardinal or relative compass direction in which one entity is located from Tehran.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: April 27, 2026, 8:38 p.m.