Triple
T280886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Premium Select |
E5350
|
entity |
| Predicate | relativePrice |
P9543
|
FINISHED |
| Object | more expensive than Main Cabin |
—
|
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: more expensive than Main Cabin | Statement: [Delta Premium Select, relativePrice, more expensive than Main Cabin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePrice Context triple: [Delta Premium Select, relativePrice, more expensive than Main Cabin]
-
A.
isPriceIndex
Indicates that a value represents a price index, expressing the relative level or change of prices compared to a reference point or period.
-
B.
purchasePrice
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
-
C.
acquisitionPrice
Indicates the monetary amount paid to acquire an asset, company, or item in a transaction.
-
D.
initialPriceTarget
Indicates the originally set price level that an analyst or entity targets for an asset before any subsequent revisions.
-
E.
actualLaunchPrice
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
- F. None of above. chosen
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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b77e028819087e606fc321219f7 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25e06dd7c8190a8cbb76cee3c6e4b |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.