Triple
T17076894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simply Lemonade |
E414370
|
entity |
| Predicate | isFromConcentrate |
P101892
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Simply Lemonade, isFromConcentrate, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromConcentrate Context triple: [Simply Lemonade, isFromConcentrate, no]
-
A.
isTypicallyConsumedFrom
Indicates that one entity is most commonly eaten or drunk using, contained in, or taken from the other entity.
-
B.
isPackagedBeverage
Indicates that an item is a beverage that has been contained or sealed within some form of packaging for distribution or consumption.
-
C.
concentrationVariant
chosen
Indicates that one entity represents a version or form of another that differs specifically in concentration level.
-
D.
hasConcentration
Indicates that one entity possesses or exhibits a specific level, strength, or density of another substance, property, or attribute.
-
E.
canBeReconstituted
Indicates that something has the capacity to be restored or returned to a prior or functional state, typically after being separated, dissolved, or broken down.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc559388190b685504cca6ed62b |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.