Triple
T17278502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staraya Ladoga |
E419453
|
entity |
| Predicate | distanceToSaintPetersburg |
P58440
|
FINISHED |
| Object | approximately 120 km east |
—
|
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 120 km east | Statement: [Staraya Ladoga, distanceToSaintPetersburg, approximately 120 km east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSaintPetersburg Context triple: [Staraya Ladoga, distanceToSaintPetersburg, approximately 120 km east]
-
A.
distanceFromSaintPetersburg
chosen
Indicates the spatial distance between a given entity and the city of Saint Petersburg.
-
B.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
C.
distanceToNizhnyNovgorod
Indicates the spatial distance between a given entity and the location of Nizhny Novgorod.
-
D.
distanceToPetersburgInMiles
Indicates the numerical distance, measured in miles, between a given entity’s location and Petersburg.
-
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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43327b048819095fbd93b2105533a |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.