Triple
T33677548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACA LifeMiles Diamond |
E862800
|
entity |
| Predicate | currentBranding |
P94018
|
FINISHED |
| Object | LifeMiles Diamond |
—
|
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: LifeMiles Diamond | Statement: [TACA LifeMiles Diamond, currentBranding, LifeMiles Diamond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentBranding Context triple: [TACA LifeMiles Diamond, currentBranding, LifeMiles Diamond]
-
A.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
B.
currentProgramBrand
chosen
Indicates that an entity is associated with the brand of the program it is currently part of or participating in.
-
C.
brandingStatus
Indicates the current state or condition of an entity’s branding, such as whether its brand identity has been defined, applied, updated, or is pending.
-
D.
exportBrand
Indicates a relationship where a brand is sold or distributed outside its home market into foreign or international markets.
-
E.
colorProcessBranding
Indicates a branding-related process that defines or applies specific colors to represent an entity’s visual identity.
- 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_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 1, 2026, 1:43 a.m.