Triple
T5534623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gudermes |
E145130
|
entity |
| Predicate | distanceToGrozny_km |
P64783
|
FINISHED |
| Object | 36 |
—
|
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: 36 | Statement: [Gudermes, distanceToGrozny_km, 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGrozny_km Context triple: [Gudermes, distanceToGrozny_km, 36]
-
A.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
B.
distanceToKutaisi_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Kutaisi.
-
C.
railDistanceFromMoscowCenter_km
Indicates the distance in kilometers from the center of Moscow to a location when traveling by rail.
-
D.
distanceFromKutaisi
Indicates the spatial distance measured from the location of Kutaisi to another specified place or entity.
-
E.
distanceFrom Tbilisi
Indicates the spatial distance between a given location or entity and the city of Tbilisi.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fa0141c81909a216be9f48d64e1 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:34 p.m.