Triple
T16668431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Askeran |
E405042
|
entity |
| Predicate | distanceToStepanakert_km |
P124198
|
FINISHED |
| Object | approximately 14 |
—
|
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 14 | Statement: [Askeran, distanceToStepanakert_km, approximately 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToStepanakert_km Context triple: [Askeran, distanceToStepanakert_km, approximately 14]
-
A.
distanceFromYerevan_km
Indicates the physical distance, measured in kilometers, between a given place and the city of Yerevan.
-
B.
distanceFromAshgabat
Indicates the measured spatial distance between a given location and the city of Ashgabat.
-
C.
distanceFrom Tbilisi
Indicates the spatial distance between a given location or entity and the city of Tbilisi.
-
D.
distanceFromAkhaltsikhe_km
Indicates the distance, measured in kilometers, between an entity and the location of Akhaltsikhe.
-
E.
distanceToGrozny_km
Indicates the physical distance, measured in kilometers, between a given location and the city of Grozny.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9e9a208190afab499897ce4361 |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:18 a.m.