Triple
T13475772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safar Flyer Miles |
E318244
|
entity |
| Predicate | canBePurchased |
P110535
|
FINISHED |
| Object | top-up miles (when offered) |
—
|
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: top-up miles (when offered) | Statement: [Safar Flyer Miles, canBePurchased, top-up miles (when offered)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePurchased Context triple: [Safar Flyer Miles, canBePurchased, top-up miles (when offered)]
-
A.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
B.
eligiblePurchasers
Indicates that certain entities are permitted or qualified to make a particular purchase under specified rules or conditions.
-
C.
isPurchasedBy
Indicates that one entity is bought or acquired in a transaction by another entity.
-
D.
canOrder
Indicates that one entity has the ability or permission to place an order for another entity or item.
-
E.
canBeObtainedFrom
Indicates that one entity is derivable, producible, or acquirable from another entity as a source or origin.
- F. None of above. chosen
Provenance (4 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf2551b48190a074fd256791742d |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:42 p.m.