Triple
T18896921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maker’s Mark Distillery |
E462231
|
entity |
| Predicate | hasAgingLocation |
P65393
|
FINISHED |
| Object | on-site rickhouses |
—
|
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: on-site rickhouses | Statement: [Maker’s Mark Distillery, hasAgingLocation, on-site rickhouses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgingLocation Context triple: [Maker’s Mark Distillery, hasAgingLocation, on-site rickhouses]
-
A.
legalAgingLocation
Indicates the place or jurisdiction in which an entity is legally aged or matures according to applicable laws or regulations.
-
B.
mayBeAgedIn
Indicates that an entity has the potential or option to undergo an aging or maturation process in a specified medium, container, or environment.
-
C.
hasMaturationLocation
chosen
Indicates the place or environment where an entity undergoes or completes its maturation process.
-
D.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
E.
positionOnAging
Indicates a stance, opinion, or policy that an entity holds regarding aging or age-related issues.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c47f6c948190918ade08bb88f1fd |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.