Triple
T25972848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oneworld Sapphire |
E645851
|
entity |
| Predicate | statusMappingExample |
P177093
|
FINISHED |
| Object | British Airways Executive Club Silver |
—
|
NE NERFINISHED |
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: British Airways Executive Club Silver | Statement: [Oneworld Sapphire, statusMappingExample, British Airways Executive Club Silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusMappingExample Context triple: [Oneworld Sapphire, statusMappingExample, British Airways Executive Club Silver]
-
A.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
B.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
C.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
statusInText
Indicates that the text explicitly states or conveys the status or condition of an entity.
- F. None of above. chosen
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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 22, 2026, 8:51 a.m.