Triple
T11459591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshkar-Ola |
E271616
|
entity |
| Predicate | distanceToMoscow_km |
P24098
|
FINISHED |
| Object | about 750 |
—
|
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 750 | Statement: [Yoshkar-Ola, distanceToMoscow_km, about 750]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMoscow_km Context triple: [Yoshkar-Ola, distanceToMoscow_km, about 750]
-
A.
distanceFromMoscow_km
chosen
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
B.
railDistanceFromMoscowCenter_km
Indicates the distance in kilometers from the center of Moscow to a location when traveling by rail.
-
C.
distanceFromSaintPetersburg
Indicates the spatial distance between a given entity and the city of Saint Petersburg.
-
D.
distanceToRostovOnDon_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Rostov-on-Don.
-
E.
distanceToArkhangelskApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Arkhangelsk.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.