Triple
T31054316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molodechno |
E791352
|
entity |
| Predicate | regionalCenterDistanceTo |
P122332
|
FINISHED |
| Object | Minsk |
—
|
NE NERFINISHED |
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: Minsk | Statement: [Molodechno, regionalCenterDistanceTo, Minsk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalCenterDistanceTo Context triple: [Molodechno, regionalCenterDistanceTo, Minsk]
-
A.
administrativeCenterDistance
Indicates the distance between an entity and the administrative center that governs or represents it.
-
B.
municipalityCenterDistance
Indicates the distance between an entity and the central point of its corresponding municipality.
-
C.
distanceFromRegionalCapital
chosen
Indicates the measured spatial distance between a given place and its corresponding regional capital.
-
D.
nearestCityCenterDistance
Indicates the distance from a given location to the closest city center.
-
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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: April 29, 2026, 9 p.m.