Triple
T8141773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medallion Qualification Dollars |
E190113
|
entity |
| Predicate | earnedFrom |
P62973
|
FINISHED |
| Object | eligible Delta-marketed flights |
—
|
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: eligible Delta-marketed flights | Statement: [Medallion Qualification Dollars, earnedFrom, eligible Delta-marketed flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earnedFrom Context triple: [Medallion Qualification Dollars, earnedFrom, eligible Delta-marketed flights]
-
A.
gainedFrom
Indicates that something is obtained, acquired, or derived as a result of a specified source or cause.
-
B.
gainedBy
Indicates that something comes to possess, obtain, or receive something else as a result of an action, process, or event.
-
C.
pointsEarnedFrom
chosen
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
-
D.
earnOn
Indicates that one entity gains income, profit, or returns as a result of another entity or activity.
-
E.
profitsFrom
Indicates that one entity gains financial or material benefit as a result of another entity’s actions, existence, or situation.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4442299881909db56f7475cbb99a |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:36 p.m.