Triple
T32233108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livny |
E823392
|
entity |
| Predicate | distanceToOryolApprox |
P204188
|
FINISHED |
| Object | ~120 km southeast |
—
|
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: ~120 km southeast | Statement: [Livny, distanceToOryolApprox, ~120 km southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToOryolApprox Context triple: [Livny, distanceToOryolApprox, ~120 km southeast]
-
A.
distanceToSmolensk
Indicates the spatial distance between a given entity and the location of Smolensk.
-
B.
distanceToNizhnyNovgorod
Indicates the spatial distance between a given entity and the location of Nizhny Novgorod.
-
C.
distanceToYoshkarOla_km
Indicates the distance, measured in kilometers, between a given entity’s location and the city of Yoshkar-Ola.
-
D.
distanceToBryansk
Indicates the spatial distance between a given entity and the location of Bryansk.
-
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. chosen
Provenance (4 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a034540e37c819087a5c75c559323d8 |
completed | May 12, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a0344e26fec8190867227f9692e92df |
completed | May 12, 2026, 3:18 p.m. |
| PDg | Predicate description generation | batch_6a0345400778819081fb3b5b71336cd7 |
completed | May 12, 2026, 3:20 p.m. |
Created at: May 1, 2026, 12:39 a.m.