Triple
T26962092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasnaya Polyana |
E679073
|
entity |
| Predicate | distanceFromSochi |
P171403
|
FINISHED |
| Object | approximately 40 kilometers |
—
|
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 40 kilometers | Statement: [Krasnaya Polyana, distanceFromSochi, approximately 40 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSochi Context triple: [Krasnaya Polyana, distanceFromSochi, approximately 40 kilometers]
-
A.
hasApproxDistanceFromSochiCenter
chosen
Indicates that one location is approximately a specified distance away from the center of Sochi.
-
B.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
C.
distanceToVladivostok_km
Indicates the physical distance, measured in kilometers, between a given location and Vladivostok.
-
D.
distanceToIrkutsk_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Irkutsk.
-
E.
distanceToSaratov_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Saratov.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: April 27, 2026, 6:32 a.m.