Triple
T21299335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laphroaig 25 Year Old |
E525012
|
entity |
| Predicate | sweetNotes |
P143642
|
FINISHED |
| Object | vanilla |
—
|
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: vanilla | Statement: [Laphroaig 25 Year Old, sweetNotes, vanilla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sweetNotes Context triple: [Laphroaig 25 Year Old, sweetNotes, vanilla]
-
A.
notableTune
Indicates that a tune is especially significant, well-known, or characteristic in relation to a particular entity.
-
B.
heartNotes
Indicates that one entity records or associates special notes, comments, or annotations about another entity in a favored or highlighted manner.
-
C.
topNote
Indicates that one entity serves as the primary or highest-level note associated with another entity.
-
D.
scriptOfNotes
Indicates that one entity is the written or notated script (e.g., musical, theatrical, or instructional notes) that documents, guides, or underlies another entity.
-
E.
baseNotes
Indicates the fundamental or underlying elements, tones, or components that serve as the primary basis for something.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385b1c548190b940ded0163ee3ca |
completed | April 21, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:05 p.m.