Triple
T15258129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schiphol terminal piers system |
E364699
|
entity |
| Predicate | hasSecuritySegregation |
P18602
|
FINISHED |
| Object | Schengen and non-Schengen flows |
—
|
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: Schengen and non-Schengen flows | Statement: [Schiphol terminal piers system, hasSecuritySegregation, Schengen and non-Schengen flows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecuritySegregation Context triple: [Schiphol terminal piers system, hasSecuritySegregation, Schengen and non-Schengen flows]
-
A.
hasSecurityRegime
Indicates that an entity is governed, protected, or controlled by a particular security regime, framework, or set of security rules.
-
B.
hasSecurityDimension
Indicates that something possesses or is associated with a particular aspect or dimension of security.
-
C.
dataSegregation
Indicates that data is kept separate or partitioned so that information from one group, context, or user is not mixed or accessible with that of another.
-
D.
hasSecurityCategory
Indicates that an entity is associated with a particular security classification or category defining its protection or access level.
-
E.
hasSecurityArea
chosen
Indicates that an entity is associated with, assigned to, or falls within a defined security-controlled area or zone.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084d11148190919eef8e55569bb9 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.