Triple
T32563130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier Miles |
E832280
|
entity |
| Predicate | associatedWithProgramName |
—
|
GENERATED |
| Object | FRONTIER Miles |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 1, 2026, 1:03 a.m.