Triple
T10412290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beverages Division |
E245420
|
entity |
| Predicate | roleWithCocaCola |
P43130
|
FINISHED |
| Object | Coca-Cola bottling partner |
—
|
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: Coca-Cola bottling partner | Statement: [Beverages Division, roleWithCocaCola, Coca-Cola bottling partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleWithCocaCola Context triple: [Beverages Division, roleWithCocaCola, Coca-Cola bottling partner]
-
A.
underlyingCompanyRole
chosen
Indicates the specific function, position, or responsibility an entity holds within or in relation to a company.
-
B.
carbonRole
Indicates the functional role or involvement that an entity has in relation to carbon within a given process, system, or context.
-
C.
roleWithCEP
Indicates that an entity holds a specific role or function that is associated with a defined Contextualized Event or Process (CEP).
-
D.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
E.
roleOfGroup
Indicates the function, responsibility, or position that a group holds within a broader context or structure.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0e17f081908fb16425f65e5808 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.