Triple
T10570460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buffalo Trace Distillery |
E249463
|
entity |
| Predicate | employsProcess |
P924
|
FINISHED |
| Object | traditional column still distillation |
—
|
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: traditional column still distillation | Statement: [Buffalo Trace Distillery, employsProcess, traditional column still distillation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employsProcess Context triple: [Buffalo Trace Distillery, employsProcess, traditional column still distillation]
-
A.
employedThrough
Indicates that an entity holds a job or work position by means of, or via the arrangement of, another entity (such as an agency, contractor, or intermediary).
-
B.
employsForm
Indicates that an entity makes use of or applies a particular form or format in carrying out an action or function.
-
C.
employedSystem
Indicates that a system is used or operated in the context of an employment or work-related arrangement.
-
D.
usedProcess
chosen
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
E.
experiencedProcess
Indicates that an entity has undergone or participated in a particular process or event.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5274678148190b7a1afc099628357 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.