Triple
T28141533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fern Pass |
E714353
|
entity |
| Predicate | distanceFromGermanBorder |
P107919
|
FINISHED |
| Object | about 25 km south |
—
|
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 25 km south | Statement: [Fern Pass, distanceFromGermanBorder, about 25 km south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromGermanBorder Context triple: [Fern Pass, distanceFromGermanBorder, about 25 km south]
-
A.
borderDistanceToGermany
chosen
Indicates the distance between an entity’s border and the border of Germany.
-
B.
distanceToRussianBorder_km
Indicates the physical distance, measured in kilometers, between a given location and the nearest point on the Russian border.
-
C.
distanceToPolishBorder
Indicates the measured distance between a given location and the nearest point on the border of Poland.
-
D.
distanceToBulgarianBorder_km
Indicates the distance, measured in kilometers, from a given location to the nearest point on the Bulgarian national border.
-
E.
EUInternalBorder
Indicates that a border lies between two member states within the European Union, where internal EU border rules apply.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
Created at: April 27, 2026, 9:53 p.m.