Triple
T28051240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sretensk |
E708824
|
entity |
| Predicate | distanceToRegionalCenter |
P122332
|
FINISHED |
| Object | located east of Chita |
—
|
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: located east of Chita | Statement: [Sretensk, distanceToRegionalCenter, located east of Chita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRegionalCenter Context triple: [Sretensk, distanceToRegionalCenter, located east of Chita]
-
A.
distanceFromRegionalCapital
chosen
Indicates the measured spatial distance between a given place and its corresponding regional capital.
-
B.
administrativeCenterDistance
Indicates the distance between an entity and the administrative center that governs or represents it.
-
C.
roadDistanceToCityCentre_km
Indicates the distance in kilometers from a location to the city centre when traveling by road.
-
D.
municipalityCenterDistance
Indicates the distance between an entity and the central point of its corresponding municipality.
-
E.
distanceFromCoreRegion
Indicates the spatial or conceptual distance between an entity and a defined core or central region.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: April 27, 2026, 8:33 p.m.