Triple
T17591550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kriva Palanka |
E428460
|
entity |
| Predicate | distanceToBulgarianBorder_km |
P128131
|
FINISHED |
| Object | approximately 13 |
—
|
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 13 | Statement: [Kriva Palanka, distanceToBulgarianBorder_km, approximately 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBulgarianBorder_km Context triple: [Kriva Palanka, distanceToBulgarianBorder_km, approximately 13]
-
A.
distanceToRussianBorder_km
Indicates the physical distance, measured in kilometers, between a given location and the nearest point on the Russian border.
-
B.
distanceFromSofia
Indicates the spatial distance between a given entity and the city of Sofia.
-
C.
distanceFromBlagoevgrad
Indicates the physical distance between a given entity or location and the city of Blagoevgrad.
-
D.
distanceToBorderWithNorthMacedonia
Indicates the measured distance from a given location to the border shared with North Macedonia.
-
E.
distanceFromStaraZagoraApproximateKm
Indicates the approximate distance, measured in kilometers, between an entity and Stara Zagora.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e79dac8190953a1ce8fc015b20 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:51 a.m.