Triple
T4243600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSA PreCheck |
E95472
|
entity |
| Predicate | screeningLocation |
P33023
|
FINISHED |
| Object | TSA security checkpoints at U.S. airports |
—
|
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: TSA security checkpoints at U.S. airports | Statement: [TSA PreCheck, screeningLocation, TSA security checkpoints at U.S. airports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screeningLocation Context triple: [TSA PreCheck, screeningLocation, TSA security checkpoints at U.S. airports]
-
A.
screeningVenue
Indicates the place or location where a screening (such as a film or event showing) takes place.
-
B.
firstScreeningLocation
chosen
Indicates the location where something (such as a person, item, or case) is initially screened or evaluated for the first time.
-
C.
examinationLocation
Indicates the place or setting where an examination or test is conducted.
-
D.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
E.
screeningType
Indicates the specific method or category of screening applied in a screening process or evaluation.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e8a676c8190ac2cb59e62613dd9 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.