Triple
T14613587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAL |
E343020
|
entity |
| Predicate | representsBrand |
P78443
|
FINISHED |
| Object | Continental Airlines brand |
—
|
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: Continental Airlines brand | Statement: [CAL, representsBrand, Continental Airlines brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsBrand Context triple: [CAL, representsBrand, Continental Airlines brand]
-
A.
brandRepresents
chosen
Indicates that a brand stands for, symbolizes, or conveys the identity, values, or characteristics of something.
-
B.
referencesBrand
Indicates that one entity mentions, cites, or otherwise refers to a specific brand in its content or context.
-
C.
formedBrand
Indicates that an entity created or established a particular brand as a distinct commercial or organizational identity.
-
D.
usesBrandCharacter
Indicates that one entity employs or features another entity’s brand character (such as a mascot or branded persona) in its materials, products, or communications.
-
E.
usedBrand
Indicates that an entity has utilized, applied, or operated a particular brand in some context.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb45264988190a1df13e8b54a85bd |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.