Triple
T26490416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kruså |
E669139
|
entity |
| Predicate | borderControlHistory |
P143681
|
FINISHED |
| Object | former customs checkpoint between Denmark and Germany |
—
|
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: former customs checkpoint between Denmark and Germany | Statement: [Kruså, borderControlHistory, former customs checkpoint between Denmark and Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderControlHistory Context triple: [Kruså, borderControlHistory, former customs checkpoint between Denmark and Germany]
-
A.
hasBorderControlHistory
chosen
Indicates that there is a documented history of actions, policies, or events related to border control involving the associated entities.
-
B.
borderControlSide
Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
-
C.
borderControlMeasure
Indicates a policy or action implemented to regulate, monitor, or restrict the movement of people or goods across a border.
-
D.
borderHistory
Indicates the historical changes, events, or status of borders between entities over time.
-
E.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 1:03 a.m.