Triple
T34290350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blanton's Single Barrel Bourbon |
E879869
|
entity |
| Predicate | stopperDesign |
P179109
|
FINISHED |
| Object | racehorse and jockey figurine |
—
|
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: racehorse and jockey figurine | Statement: [Blanton's Single Barrel Bourbon, stopperDesign, racehorse and jockey figurine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stopperDesign Context triple: [Blanton's Single Barrel Bourbon, stopperDesign, racehorse and jockey figurine]
-
A.
endDesign
Indicates that a design process, phase, or activity has been brought to its conclusion or formally terminated.
-
B.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
C.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
D.
productTypeDesigned
Indicates that one entity is the type or category of product for which another entity has been specifically designed.
-
E.
designerType
Indicates the specific kind or category of designer role associated with an entity.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:57 a.m.