Triple
T37964455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pure Kentucky Bourbon |
E947099
|
entity |
| Predicate | mustEnterBarrelAt |
P189675
|
FINISHED |
| Object | no more than 125 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: no more than 125 proof | Statement: [Pure Kentucky Bourbon, mustEnterBarrelAt, no more than 125 proof]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustEnterBarrelAt Context triple: [Pure Kentucky Bourbon, mustEnterBarrelAt, no more than 125 proof]
-
A.
hasBarrel
Indicates that one entity possesses, includes, or is equipped with a barrel as a component or feature.
-
B.
hasBarrelConfiguration
Indicates a relationship where an object is characterized by or assigned a specific arrangement or configuration of its barrel or barrels.
-
C.
hasBarrelLongerThan
Indicates that one entity’s barrel length is greater than that of another entity.
-
D.
barrelRegime
Indicates a relationship where an entity operates under, is subject to, or is characterized by a particular barrel-based regulatory or operational regime.
-
E.
barrelOrientation
Indicates the directional alignment or angle at which a barrel is positioned relative to a reference frame or object.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc7b6c2c88190ad4f58980834053c |
completed | May 6, 2026, 10:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.