Triple
T17449846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSA Pre✓ |
E424885
|
entity |
| Predicate | identifyingCode |
P3732
|
FINISHED |
| Object | Known Traveler Number |
—
|
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: Known Traveler Number | Statement: [TSA Pre✓, identifyingCode, Known Traveler Number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifyingCode Context triple: [TSA Pre✓, identifyingCode, Known Traveler Number]
-
A.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
C.
ICCCode
Indicates that an entity is associated with a specific International Criminal Court (ICC) code, identifying its classification or legal reference under ICC standards.
-
D.
ianaIdentifierType
Indicates that one entity specifies the type or category of an IANA (Internet Assigned Numbers Authority) identifier associated with another entity.
-
E.
collectionCode
Indicates the specific identifier or code assigned to the collection to which an item or resource belongs.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4513d00f48190802a3bdc8c8f4db5 |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.