Triple
T9241435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mabuhay Miles |
E222066
|
entity |
| Predicate | eliteQualification |
P30231
|
FINISHED |
| Object | based on flown miles and/or sectors |
—
|
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: based on flown miles and/or sectors | Statement: [Mabuhay Miles, eliteQualification, based on flown miles and/or sectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteQualification Context triple: [Mabuhay Miles, eliteQualification, based on flown miles and/or sectors]
-
A.
runnerUpQualification
Indicates that an entity attains a qualifying position or status specifically by being a runner-up in a competition or selection process.
-
B.
eliteField
Indicates that the entity is associated with a highly selective or top-tier field, domain, or area of specialization.
-
C.
qualifyingEvent
chosen
Indicates that an event meets specific conditions or criteria that make an entity eligible for a particular status, action, or outcome.
-
D.
qualificationHeld
Indicates that an entity possesses or has obtained a particular qualification or credential.
-
E.
usesQualificationSystem
Indicates that an entity applies or relies on a specific qualification system as part of its processes or operations.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cd03ea9d90819096f9ca5321dffd56 |
completed | April 1, 2026, 11:39 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:30 p.m.