Triple
T5052005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab Aero |
E113806
|
entity |
| Predicate | brandingEmphasis |
P14764
|
FINISHED |
| Object | sportiness |
—
|
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: sportiness | Statement: [Saab Aero, brandingEmphasis, sportiness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandingEmphasis Context triple: [Saab Aero, brandingEmphasis, sportiness]
-
A.
brandingNote
Indicates that an entity has an associated note or comment specifically about its branding, such as style, usage, or presentation guidelines.
-
B.
brandingFeature
chosen
Indicates that one entity serves as a branding-related characteristic, element, or attribute that helps define or distinguish another entity’s brand identity.
-
C.
marketingNameEmphasizes
Indicates that a marketing name highlights or draws special attention to a particular feature, attribute, or aspect of something.
-
D.
brandingMeaning
Indicates the conceptual message, values, or identity that a brand is intended to convey or represent.
-
E.
brandingRole
Indicates the specific function or responsibility an entity has in creating, managing, or representing a brand within a branding 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7426fc8081908a8227f73168c235 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.