Triple
T36878744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bromo-Seltzer |
E911414
|
entity |
| Predicate | hasNotablePackaging |
P120559
|
FINISHED |
| Object | blue glass bottle |
—
|
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: blue glass bottle | Statement: [Bromo-Seltzer, hasNotablePackaging, blue glass bottle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePackaging Context triple: [Bromo-Seltzer, hasNotablePackaging, blue glass bottle]
-
A.
notablePackagingDesign
chosen
Indicates that an entity is recognized for having a distinctive, noteworthy, or otherwise significant packaging design.
-
B.
hasFictionalPackaging
Indicates that an item is presented or wrapped in packaging that is imaginary, simulated, or not used in real-world distribution.
-
C.
commonPackagingFeatures
Indicates that two or more products share the same or very similar packaging characteristics or design elements.
-
D.
packagingStyle
Indicates the manner or format in which a product or item is packaged or presented.
-
E.
packaging
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.