Triple
T6363119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JAL Mileage Bank |
E143157
|
entity |
| Predicate | eliteStatusBasis |
P9729
|
FINISHED |
| Object | flight mileage |
—
|
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: flight mileage | Statement: [JAL Mileage Bank, eliteStatusBasis, flight mileage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteStatusBasis Context triple: [JAL Mileage Bank, eliteStatusBasis, flight mileage]
-
A.
eliteField
Indicates that the entity is associated with a highly selective or top-tier field, domain, or area of specialization.
-
B.
eligibilityLevel
chosen
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
C.
elite
Indicates that the subject belongs to a select, superior, or highly privileged subset within a larger group or category.
-
D.
membershipLevelAbove
Indicates that one entity’s membership level is ranked higher or more privileged than another entity’s membership level.
-
E.
isEliteUnit
Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680d51a4819098a6bcd3dfd73be4 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.