Triple
T28052603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elevate |
E708867
|
entity |
| Predicate | pointsEarningMethod |
P123880
|
FINISHED |
| Object | distance flown |
—
|
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: distance flown | Statement: [Elevate, pointsEarningMethod, distance flown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsEarningMethod Context triple: [Elevate, pointsEarningMethod, distance flown]
-
A.
pointsEarnedFrom
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
-
B.
pointsAwarded
Indicates that a specified number of points has been granted to an entity as a result of some action or event.
-
C.
pointAllocationMethod
chosen
Indicates how points are assigned or distributed within a given system or process.
-
D.
loyaltyProgramEarnings
Indicates the amount or details of rewards or benefits a participant accrues within a loyalty or rewards program.
-
E.
usesPointsSystem
Indicates that an entity operates or functions based on a structured points-based system for evaluation, rewards, or progression.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 8:34 p.m.