Triple
T7908280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pravdinsk |
E183630
|
entity |
| Predicate | distanceFromKaliningrad |
P76355
|
FINISHED |
| Object | approximately 53 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: approximately 53 km southeast | Statement: [Pravdinsk, distanceFromKaliningrad, approximately 53 km southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromKaliningrad Context triple: [Pravdinsk, distanceFromKaliningrad, approximately 53 km southeast]
-
A.
distanceToKaliningradApprox
chosen
Indicates an approximate distance between a given entity’s location and Kaliningrad.
-
B.
distanceFromSaintPetersburg
Indicates the spatial distance between a given entity and the city of Saint Petersburg.
-
C.
distanceToArkhangelskApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Arkhangelsk.
-
D.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
E.
distanceToWarsaw
Indicates the spatial distance between a given entity’s location and the city of Warsaw.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a59de00819099f1ce02bb469e75 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:03 p.m.