Triple
T15923133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evian |
E386140
|
entity |
| Predicate | notablePackagingDesign |
P120559
|
FINISHED |
| Object | curved bottle shape |
—
|
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: curved bottle shape | Statement: [Evian, notablePackagingDesign, curved bottle shape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePackagingDesign Context triple: [Evian, notablePackagingDesign, curved bottle shape]
-
A.
packaging
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
-
B.
notablePackage
Indicates that an entity is a particularly significant, well-known, or otherwise noteworthy package within its domain.
-
C.
hasDesignRecognition
Indicates that an entity has received recognition, awards, or notable acknowledgment specifically for its design.
-
D.
notableCover
Indicates that one entity is a particularly well-known or significant cover version or adaptation of another entity.
-
E.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
- F. None of above. chosen
Provenance (4 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e172b213e481909ee0c05e16229a26 |
completed | April 16, 2026, 11:37 p.m. |
Created at: April 10, 2026, 4:52 a.m.