Triple
T5607333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nestlé Waters |
E147264
|
entity |
| Predicate | usesDistributionChannels |
P8091
|
FINISHED |
| Object | retail |
—
|
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: retail | Statement: [Nestlé Waters, usesDistributionChannels, retail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDistributionChannels Context triple: [Nestlé Waters, usesDistributionChannels, retail]
-
A.
allowsDistribution
Indicates that one entity grants permission for another entity to distribute or disseminate something (e.g., content, products, or data).
-
B.
distributesIn
chosen
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
-
C.
hasDistributionPartners
Indicates that an entity collaborates with other entities to distribute its products or services.
-
D.
hasDistributions
Indicates that an entity is associated with one or more distributions through which it is delivered, provided, or made available.
-
E.
distributorType
Indicates the specific category or role of a distributor in relation to the distribution of a product or service.
- 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_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. |
Created at: March 22, 2026, 3:39 p.m.