Triple
T14373033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenmorangie |
E356401
|
entity |
| Predicate | usesWashbacks |
P113779
|
FINISHED |
| Object | wooden washbacks |
—
|
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: wooden washbacks | Statement: [Glenmorangie, usesWashbacks, wooden washbacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWashbacks Context triple: [Glenmorangie, usesWashbacks, wooden washbacks]
-
A.
usesIncentive
Indicates that one entity employs or applies an incentive (such as a reward, benefit, or motivation) to influence the behavior or decisions of another entity.
-
B.
backsUp
Indicates that one entity provides support, reinforcement, or confirmation for another entity’s actions, statements, or position.
-
C.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9007184c8190aebb003cb6548cc8 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:15 a.m.