Triple
T33319763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Airlines MileagePlus |
E853105
|
entity |
| Predicate | allowsMileagePurchase |
P98615
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [United Airlines MileagePlus, allowsMileagePurchase, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsMileagePurchase Context triple: [United Airlines MileagePlus, allowsMileagePurchase, true]
-
A.
vehicleRestrictionMile
Indicates a restriction or limitation that applies to vehicles at a specific mile point or mile marker along a route.
-
B.
milesCanBePurchased
chosen
Indicates that a certain number of miles are eligible to be bought, typically in exchange for money or points.
-
C.
mileageAccrual
Indicates the accumulation or earning of mileage (such as distance-based points or credits) as a result of certain actions or usage.
-
D.
basedOnVehicle
Indicates that one entity is derived from, modeled after, or otherwise conceptually or functionally based on a particular vehicle.
-
E.
hasVehicularUse
Indicates that something is used for, intended for, or associated with operation by vehicles or vehicular traffic.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 1:33 a.m.