Triple
T37964456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pure Kentucky Bourbon |
E947099
|
entity |
| Predicate | mustBeBottledAt |
P178912
|
FINISHED |
| Object | at least 80 proof |
—
|
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: at least 80 proof | Statement: [Pure Kentucky Bourbon, mustBeBottledAt, at least 80 proof]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustBeBottledAt Context triple: [Pure Kentucky Bourbon, mustBeBottledAt, at least 80 proof]
-
A.
riservaMinimumAgingRequirement
Indicates that a product labeled as "riserva" must undergo at least a specified minimum aging period before it can be released or designated as such.
-
B.
bottledAs
Indicates that a substance or product has been placed into a bottle in a particular form, configuration, or under a specific label or brand.
-
C.
bottlingProof
chosen
Indicates the specific alcohol proof at which a beverage is bottled.
-
D.
minimumAgingBottle
Indicates the minimum amount of time a bottle must age (or be stored) before it is considered ready or valid for its intended use.
-
E.
bottledBy
Indicates that one entity is responsible for placing another entity into bottles or containers for packaging or distribution.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:20 p.m.