Triple
T33796463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACA LifeMiles Elite |
E866086
|
entity |
| Predicate | statusWithinProgram |
P94017
|
FINISHED |
| Object | elite member status |
—
|
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: elite member status | Statement: [TACA LifeMiles Elite, statusWithinProgram, elite member status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusWithinProgram Context triple: [TACA LifeMiles Elite, statusWithinProgram, elite member status]
-
A.
statusLevelWithinProgram
chosen
Indicates the relative rank or standing an entity holds within a specific program.
-
B.
statusEquivalenceWithinProgram
Indicates that two entities hold the same status or standing within the context of a particular program.
-
C.
subjectToProgram
Indicates that an entity is governed, regulated, or affected by a specific program, policy, or systematic initiative.
-
D.
authorizedUnderProgram
Indicates that an entity’s action, status, or participation is permitted or governed according to the rules or provisions of a specific program.
-
E.
statusProgramType
Indicates the type or category of program associated with a given status.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 1, 2026, 1:46 a.m.