Triple
T17381900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Club miles |
E422588
|
entity |
| Predicate | earnedThrough |
P29971
|
FINISHED |
| Object | revenue flights on Virgin Atlantic |
—
|
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: revenue flights on Virgin Atlantic | Statement: [Flying Club miles, earnedThrough, revenue flights on Virgin Atlantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earnedThrough Context triple: [Flying Club miles, earnedThrough, revenue flights on Virgin Atlantic]
-
A.
pointsEarnedFrom
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
-
B.
progressedBy
Indicates that an activity, process, or state advances or moves forward as a result of the actions or influence of a specified agent or factor.
-
C.
gainedBy
Indicates that something comes to possess, obtain, or receive something else as a result of an action, process, or event.
-
D.
gainedFrom
chosen
Indicates that something is obtained, acquired, or derived as a result of a specified source or cause.
-
E.
earnOn
Indicates that one entity gains income, profit, or returns as a result of another entity or activity.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a86d8cc81909281b22f5da87d70 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.