Triple
T19739330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stitzel-Weller Distillery |
E474070
|
entity |
| Predicate | warehouseUse |
P137152
|
FINISHED |
| Object | aging of Diageo bourbon stocks |
—
|
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: aging of Diageo bourbon stocks | Statement: [Stitzel-Weller Distillery, warehouseUse, aging of Diageo bourbon stocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warehouseUse Context triple: [Stitzel-Weller Distillery, warehouseUse, aging of Diageo bourbon stocks]
-
A.
warehouseType
Indicates the specific category or classification of a warehouse based on its function, storage characteristics, or operational role.
-
B.
storageFacility
Indicates a relationship where one entity serves as a place or facility used to store another entity or its items.
-
C.
store
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
D.
canBeStoredOn
Indicates that one entity is capable of being placed, kept, or maintained on another entity as a storage location.
-
E.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e651607e388190bbb2aaed252820fe |
completed | April 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.