Triple
T25459292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Miles Gold tier |
E637998
|
entity |
| Predicate | correspondsToAllianceTier |
P76249
|
FINISHED |
| Object | SkyTeam Elite Plus |
—
|
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: SkyTeam Elite Plus | Statement: [Eastern Miles Gold tier, correspondsToAllianceTier, SkyTeam Elite Plus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToAllianceTier Context triple: [Eastern Miles Gold tier, correspondsToAllianceTier, SkyTeam Elite Plus]
-
A.
allianceTierNames
Indicates the specific tier or level designation assigned within an alliance structure.
-
B.
statusMatchLevelInAlliance
chosen
Indicates the degree to which two entities’ statuses align or correspond within the context of an alliance.
-
C.
involvesAlliance
Indicates that there exists a cooperative or strategic alliance relationship between the referenced entities.
-
D.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
E.
allianceCompatibility
Indicates that two or more entities are suitable or well-matched to form or maintain an alliance based on their respective attributes, goals, or constraints.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7296cd08190b5dde235602c4c01 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 2:11 p.m.