Triple
T23233667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schengen departures area |
E581228
|
entity |
| Predicate | connectedTo |
P37
|
FINISHED |
| Object | Schengen arrival gates |
—
|
NE NERFINISHED |
How this triple was built (3 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: Schengen arrival gates | Statement: [Schengen departures area, connectedTo, Schengen arrival gates]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schengen arrival gates Context triple: [Schengen departures area, connectedTo, Schengen arrival gates]
-
A.
Schengen departures area
The Schengen departures area is a section of an airport terminal dedicated to passengers traveling between countries in the Schengen Area, where border checks are typically not required.
-
B.
Schengen external border
The Schengen external border is the outer boundary of the Schengen Area where full passport and customs controls are applied to regulate entry and exit between Schengen and non-Schengen countries.
-
C.
Schengen–Perl border crossing
The Schengen–Perl border crossing is a notable road and pedestrian crossing over the Moselle River linking the village of Schengen in Luxembourg with Perl in Germany, symbolizing European open-border integration.
-
D.
Schengen Information System
The Schengen Information System is a large-scale European security and border management database that enables Schengen states to share alerts on persons and objects for purposes such as border control and law enforcement.
-
E.
Schengen internal border
A Schengen internal border is a frontier between two countries within the Schengen Area where systematic border checks have been abolished, allowing largely unrestricted cross-border movement.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Schengen arrival gates Target entity description: Schengen arrival gates are airport entry points within the Schengen Area where passengers arriving from other Schengen countries disembark and enter the common border-free zone without passport control.
-
A.
Schengen departures area
The Schengen departures area is a section of an airport terminal dedicated to passengers traveling between countries in the Schengen Area, where border checks are typically not required.
-
B.
Schengen external border
The Schengen external border is the outer boundary of the Schengen Area where full passport and customs controls are applied to regulate entry and exit between Schengen and non-Schengen countries.
-
C.
Schengen–Perl border crossing
The Schengen–Perl border crossing is a notable road and pedestrian crossing over the Moselle River linking the village of Schengen in Luxembourg with Perl in Germany, symbolizing European open-border integration.
-
D.
Schengen Information System
The Schengen Information System is a large-scale European security and border management database that enables Schengen states to share alerts on persons and objects for purposes such as border control and law enforcement.
-
E.
Schengen internal border
chosen
A Schengen internal border is a frontier between two countries within the Schengen Area where systematic border checks have been abolished, allowing largely unrestricted cross-border movement.
- F. None of above.
Provenance (2 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192e7bed88190b914b238c5f49860 |
completed | April 29, 2026, 5:11 a.m. |
Created at: April 17, 2026, 4:09 p.m.