Triple
T4243629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Known Traveler Number system |
E95473
|
entity |
| Predicate | typeOfNumber |
P4426
|
FINISHED |
| Object | unique traveler identifier |
—
|
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: unique traveler identifier | Statement: [Known Traveler Number system, typeOfNumber, unique traveler identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfNumber Context triple: [Known Traveler Number system, typeOfNumber, unique traveler identifier]
-
A.
typeOf
Indicates that one entity is a specific kind, class, or category instance of another more general entity.
-
B.
hasNumberCategory
chosen
Indicates that an entity is associated with a specific numerical classification or type.
-
C.
typeOfDate
Indicates that one entity specifies the category or kind of date (e.g., start date, end date, due date) that characterizes another date-related entity or value.
-
D.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
E.
typeOfCondition
Indicates that one condition is a specific kind, category, or subtype of another condition.
- 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.