Triple
T32563130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier Miles |
E832280
|
entity |
| Predicate | associatedWithProgramName |
P16656
|
FINISHED |
| Object | FRONTIER Miles |
E196246
|
NE 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: FRONTIER Miles | Statement: [Frontier Miles, associatedWithProgramName, FRONTIER Miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithProgramName Context triple: [Frontier Miles, associatedWithProgramName, FRONTIER Miles]
-
A.
associatedWithProgramOfNotableBearer
Indicates that an entity is connected to, or involved with, the program (e.g., project, initiative, or activity) that is linked to a notable bearer.
-
B.
belongsToProgram
chosen
Indicates that an entity is a member of, or is associated with, a specific program.
-
C.
associatedWithUpgradePrograms
Indicates a relationship where an entity is linked to, participates in, or is covered by one or more upgrade programs.
-
D.
associatedWithVendorProgram
Indicates that an entity has a formal relationship or participation connection with a specific vendor’s program.
-
E.
linkedProgram
Indicates that one program is associated or connected to another program in a meaningful or dependent way.
- F. None of above.
Provenance (4 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347b95a034819081d54e4669b5cb8f |
completed | June 18, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:03 a.m.