Triple
T5607615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnation |
E147270
|
entity |
| Predicate | hasBrandRecognitionFor |
P64618
|
FINISHED |
| Object | cooking uses |
—
|
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: cooking uses | Statement: [Carnation, hasBrandRecognitionFor, cooking uses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandRecognitionFor Context triple: [Carnation, hasBrandRecognitionFor, cooking uses]
-
A.
hasBrandIdentityElement
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
B.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
C.
hasGlobalBrand
Indicates that an entity possesses a brand that is recognized and operates across multiple countries or worldwide.
-
D.
brand
Indicates that one entity is the commercial brand or label under which another entity (such as a product, service, or organization) is marketed or identified.
-
E.
competitiveBrandName
Indicates that one brand name is in a competitive relationship with another brand name in the same market or product space.
- F. None of above. chosen
Provenance (4 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fd1b2c81908da154f7e11b90d8 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:39 p.m.