Triple
T3889341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coca-Cola Zero Sugar |
E88019
|
entity |
| Predicate | hasLabelClaim |
P16616
|
FINISHED |
| Object | zero sugar |
—
|
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: zero sugar | Statement: [Coca-Cola Zero Sugar, hasLabelClaim, zero sugar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLabelClaim Context triple: [Coca-Cola Zero Sugar, hasLabelClaim, zero sugar]
-
A.
hasLabel
Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
-
B.
hasLabelSet
Indicates that an entity is associated with a specific collection or set of labels.
-
C.
attributeClaim
chosen
Indicates that one entity asserts or specifies a particular attribute or property about another entity.
-
D.
hasCentralClaim
Indicates that one entity presents or embodies the main assertion, thesis, or primary point made by another entity.
-
E.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecaee7148190ada451ccfc6582ee |
completed | March 9, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.