Triple
T9972702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FRONTIER Miles |
E196246
|
entity |
| Predicate | programOperatorType |
P21524
|
FINISHED |
| Object | low-cost carrier |
—
|
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: low-cost carrier | Statement: [FRONTIER Miles, programOperatorType, low-cost carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programOperatorType Context triple: [FRONTIER Miles, programOperatorType, low-cost carrier]
-
A.
typicalOperatorType
chosen
Indicates the usual or most common type or category of operator associated with a given entity or context.
-
B.
typicalOperator
Indicates that an entity commonly or normally performs operations on, or acts upon, another entity in a standard or expected manner.
-
C.
operatorVariant
Indicates a relationship where one operator is an alternative or modified form of another, typically differing in implementation, configuration, or usage while serving a related function.
-
D.
operatorBase
Indicates that one entity serves as the primary or foundational operator for another entity or operation.
-
E.
typeOfOperation
Indicates the specific kind or category of operation being performed or referenced in a given context.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7bb03688190a3f4fc1988b8fafa |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.