Triple
T8141805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medallion Qualification Miles |
E190114
|
entity |
| Predicate | canBeEarnedVia |
P25436
|
FINISHED |
| Object | flown travel |
—
|
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: flown travel | Statement: [Medallion Qualification Miles, canBeEarnedVia, flown travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeEarnedVia Context triple: [Medallion Qualification Miles, canBeEarnedVia, flown travel]
-
A.
canBeEarnedBy
Indicates that something (such as a reward, status, or resource) is obtainable through the actions, efforts, or qualifications of a particular entity.
-
B.
canEarnOn
Indicates that an entity is able or permitted to receive or generate earnings from another entity, source, or activity.
-
C.
canBeAwardedTo
Indicates that something is eligible to receive or be granted a particular award, honor, or recognition.
-
D.
canBeObtainedFrom
chosen
Indicates that one entity is derivable, producible, or acquirable from another entity as a source or origin.
-
E.
canBeAwarded
Indicates that an entity is eligible to receive or be granted a particular award, prize, or honor.
- 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.