Triple
T16697770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istra |
E405759
|
entity |
| Predicate | distanceToMoscowByRail |
P65643
|
FINISHED |
| Object | approximately 56 km |
—
|
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 56 km | Statement: [Istra, distanceToMoscowByRail, approximately 56 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMoscowByRail Context triple: [Istra, distanceToMoscowByRail, approximately 56 km]
-
A.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
B.
distanceToByRail
chosen
Indicates the distance between two locations when traveling via railway routes.
-
C.
distanceDirectionFromMoscow
Indicates the relative distance and compass direction of one location measured from Moscow.
-
D.
distanceToSmolensk
Indicates the spatial distance between a given entity and the location of Smolensk.
-
E.
railDistanceFromMoscowCenter_km
Indicates the distance in kilometers from the center of Moscow to a location when traveling by rail.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3832e93c48190a594c498e9cc901a |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.