Triple
T22804463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanaig |
E564493
|
entity |
| Predicate | hasCaskInfluence |
P52924
|
FINISHED |
| Object | bourbon cask |
—
|
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: bourbon cask | Statement: [Sanaig, hasCaskInfluence, bourbon cask]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaskInfluence Context triple: [Sanaig, hasCaskInfluence, bourbon cask]
-
A.
hasSubstrateInfluenceOn
Indicates that one substrate affects, modifies, or determines the behavior, activity, or properties of another entity or process.
-
B.
typicalCaskType
chosen
Indicates the usual or most commonly used type of cask associated with a given entity or context.
-
C.
hasRetroInfluence
Indicates that something is influenced by or incorporates stylistic or conceptual elements from an earlier time or past era.
-
D.
hasPossibleInfluence
Indicates that one entity may have an effect on, contribute to, or shape the state, behavior, or outcome of another entity, without asserting that this influence is definite or direct.
-
E.
hasCatalyst
Indicates that a process, reaction, or transformation occurs with the involvement of a specific catalyst that facilitates or accelerates it.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5b37cc8190a41d8f304ba8d609 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.