Triple
T26116395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etihad Guest Miles |
E658834
|
entity |
| Predicate | canBePurchasedAs |
P110535
|
FINISHED |
| Object | buy 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: buy miles | Statement: [Etihad Guest Miles, canBePurchasedAs, buy miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePurchasedAs Context triple: [Etihad Guest Miles, canBePurchasedAs, buy miles]
-
A.
canBePurchased
chosen
Indicates that one entity is available to be bought or acquired in exchange for payment by another entity.
-
B.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
C.
canBeObtainedFrom
Indicates that one entity is derivable, producible, or acquirable from another entity as a source or origin.
-
D.
buyIn
Indicates that one party purchases or acquires an ownership stake, participation, or commitment in something initiated or owned by another party.
-
E.
purchasedIn
Indicates that a purchasing event occurred within or at a specific location or context (such as a store, city, or country).
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 26, 2026, 8:05 p.m.