Triple
T25972810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oneworld Ruby |
E645850
|
entity |
| Predicate | allianceBranding |
P96100
|
FINISHED |
| Object | Oneworld Ruby logo |
—
|
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: Oneworld Ruby logo | Statement: [Oneworld Ruby, allianceBranding, Oneworld Ruby logo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceBranding Context triple: [Oneworld Ruby, allianceBranding, Oneworld Ruby logo]
-
A.
allianceBrandOf
Indicates a relationship where one brand is part of, or operates under, a broader alliance or group brand.
-
B.
brandingAuthority
Indicates that one entity has the recognized power or right to define, control, or approve the branding (name, logo, identity, or brand usage) of another entity or product.
-
C.
brandingCollaboration
Indicates a cooperative relationship where entities work together on branding-related activities, such as co-developing or jointly promoting brand identity, image, or marketing materials.
-
D.
allianceName
Indicates the designated name or title assigned to an alliance between entities.
-
E.
brandingFamily
chosen
Indicates that one entity belongs to, or is associated with, a particular brand family or group under a shared branding strategy.
- 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_69f605055e68819098ab1a9d803ce6a3 |
completed | May 2, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:51 a.m.