Triple
T19018702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6E Rewards |
E465424
|
entity |
| Predicate | pointsUsage |
P64949
|
FINISHED |
| Object | flight redemptions |
—
|
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: flight redemptions | Statement: [6E Rewards, pointsUsage, flight redemptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsUsage Context triple: [6E Rewards, pointsUsage, flight redemptions]
-
A.
badgeUsage
Indicates how and in what context a badge is applied, displayed, or utilized in relation to an entity or activity.
-
B.
tracksUsage
Indicates that one entity monitors, records, or keeps a log of how another entity is used over time.
-
C.
gridUsage
Indicates how much and in what way an entity consumes or relies on a shared grid-based resource, such as an electrical or data grid.
-
D.
usesPointsSystem
chosen
Indicates that an entity operates or functions based on a structured points-based system for evaluation, rewards, or progression.
-
E.
pointsEarnedFrom
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6dd0e6c8190a6dc6af1f7901299 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.