Triple
T17334311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles (Flying Blue) |
E420894
|
entity |
| Predicate | mayExpire |
P47854
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Miles (Flying Blue), mayExpire, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayExpire Context triple: [Miles (Flying Blue), mayExpire, yes]
-
A.
canExpire
chosen
Indicates that the subject has the property or status of being able to end, lapse, or become invalid after a certain time or condition is met.
-
B.
consequenceOfExpiry
Indicates that something occurs as a direct result of an expiry event or the state of having expired.
-
C.
mayDelay
Indicates that one entity has the potential or permission to cause a postponement or slowing of another entity, event, or process.
-
D.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
E.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a106df48190a50f96febc13cde7 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.