Triple
T27513730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gołdap |
E694487
|
entity |
| Predicate | distanceToKaliningrad |
P76355
|
FINISHED |
| Object | about 70 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: about 70 km | Statement: [Gołdap, distanceToKaliningrad, about 70 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKaliningrad Context triple: [Gołdap, distanceToKaliningrad, about 70 km]
-
A.
distanceToKaliningradApprox
chosen
Indicates an approximate distance between a given entity’s location and Kaliningrad.
-
B.
distanceToVitebsk_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Vitebsk.
-
C.
distanceFromSaintPetersburg
Indicates the spatial distance between a given entity and the city of Saint Petersburg.
-
D.
distanceToVladivostok_km
Indicates the physical distance, measured in kilometers, between a given location and Vladivostok.
-
E.
distanceToArkhangelskApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Arkhangelsk.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: April 27, 2026, 1:17 p.m.