Triple
T33319708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Airlines MileagePlus |
E853105
|
entity |
| Predicate | primaryCurrencyName |
P86202
|
FINISHED |
| Object | MileagePlus miles |
E47889
|
NE 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: MileagePlus miles | Statement: [United Airlines MileagePlus, primaryCurrencyName, MileagePlus miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCurrencyName Context triple: [United Airlines MileagePlus, primaryCurrencyName, MileagePlus miles]
-
A.
primaryListingCurrency
Indicates the currency in which an asset, security, or item is primarily listed or denominated for trading or reference.
-
B.
currencyGiven
Indicates that one entity transfers or provides money or a monetary unit to another entity.
-
C.
officialNameOfCurrency
chosen
Indicates the officially designated name of a particular currency used by an entity.
-
D.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
-
E.
localCurrency
Indicates that a particular currency is officially used or recognized as the standard medium of exchange within a specific locality, region, or country.
- F. None of above.
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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3543321c908190ab0eeb737cbfd02e |
completed | June 19, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:33 a.m.