Triple
T31755871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Gateway |
E810553
|
entity |
| Predicate | securityScreeningAvailable |
P18242
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [International Gateway, securityScreeningAvailable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityScreeningAvailable Context triple: [International Gateway, securityScreeningAvailable, yes]
-
A.
hasSecurityScreening
chosen
Indicates that an entity is subject to, or has undergone, a security screening process.
-
B.
securityStatus
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
-
C.
securityBarrierStatus
Indicates the current operational state or condition of a security barrier (e.g., whether it is active, inactive, open, closed, or otherwise engaged).
-
D.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
E.
hasScreened
Indicates that one entity has shown, displayed, or evaluated another entity, typically in the context of presenting media or conducting a review or check.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.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 30, 2026, 11:29 p.m.