Triple
T11204159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles&Go |
E265116
|
entity |
| Predicate | allowsEarning |
P67161
|
FINISHED |
| Object | award miles |
—
|
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: award miles | Statement: [Miles&Go, allowsEarning, award miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsEarning Context triple: [Miles&Go, allowsEarning, award miles]
-
A.
canEarnOn
chosen
Indicates that an entity is able or permitted to receive or generate earnings from another entity, source, or activity.
-
B.
canBeEarnedBy
Indicates that something (such as a reward, status, or resource) is obtainable through the actions, efforts, or qualifications of a particular entity.
-
C.
earnOn
Indicates that one entity gains income, profit, or returns as a result of another entity or activity.
-
D.
alsoEligible
Indicates that an entity qualifies for an additional option, status, or benefit beyond its primary or initial eligibility.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d355c481908fc3d555b596314d |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.