Triple
T18942900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrowhead Water |
E463430
|
entity |
| Predicate | formerlyBrandOf |
P1501
|
FINISHED |
| Object | Nestlé Waters North America portfolio |
—
|
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: Nestlé Waters North America portfolio | Statement: [Arrowhead Water, formerlyBrandOf, Nestlé Waters North America portfolio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyBrandOf Context triple: [Arrowhead Water, formerlyBrandOf, Nestlé Waters North America portfolio]
-
A.
formerBrand
chosen
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
B.
usedBrandOf
Indicates that one entity made use of or operated an item, product, or service associated with a particular brand.
-
C.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
-
D.
formedBrand
Indicates that an entity created or established a particular brand as a distinct commercial or organizational identity.
-
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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3ed847c8190a911a61673608a5c |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.