Triple
T34224036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smirnoff |
E877998
|
entity |
| Predicate | availableFormats |
P54872
|
FINISHED |
| Object | bottled spirits |
—
|
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: bottled spirits | Statement: [Smirnoff, availableFormats, bottled spirits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableFormats Context triple: [Smirnoff, availableFormats, bottled spirits]
-
A.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
B.
containerFormats
chosen
Indicates that one entity serves as a container or packaging format used to hold, encapsulate, or structure the contents of another entity.
-
C.
previousFormats
Indicates that an entity has had one or more earlier or prior formats or versions it existed in before its current form.
-
D.
pluginFormats
Indicates that one entity supports, uses, or is compatible with certain plugin formats associated with another entity.
-
E.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710846ef4819092c9a75057a0d767 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.