Triple
T25972798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oneworld Ruby |
E645850
|
entity |
| Predicate | statusMappedFrom |
P11519
|
FINISHED |
| Object | American Airlines AAdvantage Gold |
—
|
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: American Airlines AAdvantage Gold | Statement: [Oneworld Ruby, statusMappedFrom, American Airlines AAdvantage Gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusMappedFrom Context triple: [Oneworld Ruby, statusMappedFrom, American Airlines AAdvantage Gold]
-
A.
statusDerivedFrom
Indicates that one entity’s status is obtained, inferred, or inherited from the status of another entity.
-
B.
mapped
chosen
Indicates that one entity has been associated, corresponded, or linked systematically to another according to some defined mapping or alignment.
-
C.
representedFrom
Indicates that one entity serves as a representation or depiction of another entity.
-
D.
statusRecordedBy
Indicates that the status of an entity was documented or captured by a specific agent or system.
-
E.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 22, 2026, 8:51 a.m.