Triple
T33677387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegean Miles+Bonus Silver |
E862796
|
entity |
| Predicate | statusLevelInAlliance |
P76249
|
FINISHED |
| Object | Star Alliance 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: Star Alliance Silver | Statement: [Aegean Miles+Bonus Silver, statusLevelInAlliance, Star Alliance Silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusLevelInAlliance Context triple: [Aegean Miles+Bonus Silver, statusLevelInAlliance, Star Alliance Silver]
-
A.
statusMatchLevelInAlliance
chosen
Indicates the degree to which two entities’ statuses align or correspond within the context of an alliance.
-
B.
allianceStatus
Indicates the formal or informal cooperative relationship between entities, such as whether they are allies, neutral, or adversarial.
-
C.
statusInLeague
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
D.
statusLevelBasedOn
Indicates that one entity’s status level is determined or derived from another specified factor or entity.
-
E.
allianceTierNames
Indicates the specific tier or level designation assigned within an alliance structure.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: May 1, 2026, 1:43 a.m.