Triple
T6681307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Terminal (Tampa International Airport) |
E151985
|
entity |
| Predicate | hasSecurityCheckpointFor |
P22957
|
FINISHED |
| Object | access to airsides |
—
|
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: access to airsides | Statement: [Main Terminal (Tampa International Airport), hasSecurityCheckpointFor, access to airsides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityCheckpointFor Context triple: [Main Terminal (Tampa International Airport), hasSecurityCheckpointFor, access to airsides]
-
A.
hasSecurityScreening
Indicates that an entity is subject to, or has undergone, a security screening process.
-
B.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
C.
hasSecurityPresence
chosen
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
D.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
E.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c0aa8c5c8190a302b261f11b70cb |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0b6d00819086205b8ce30dd045 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:04 p.m.