Triple
T26556003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Padborg border crossing |
E671808
|
entity |
| Predicate | borderDirectionFromGermany |
P182816
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Padborg border crossing, borderDirectionFromGermany, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDirectionFromGermany Context triple: [Padborg border crossing, borderDirectionFromGermany, north]
-
A.
borderDistanceToGermany
Indicates the distance between an entity’s border and the border of Germany.
-
B.
borderDirectionFromUS
Indicates the compass direction in which a country or region lies relative to the United States along their shared border.
-
C.
borderDirectionFromDenmark
chosen
Indicates the compass direction in which another country or region lies relative to Denmark along their shared border.
-
D.
borderDirectionFromCapital
Indicates the compass direction from a country's capital city to a specified border or neighboring entity.
-
E.
countryBorderDirection
Indicates the cardinal or relative direction in which one country lies in relation to the border it shares with another country.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 1:50 a.m.