Triple
T31704153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premiers Crus (Sauternes and Barsac) |
E809134
|
entity |
| Predicate | notableAromaDescriptors |
P149764
|
FINISHED |
| Object | honey |
—
|
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: honey | Statement: [Premiers Crus (Sauternes and Barsac), notableAromaDescriptors, honey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAromaDescriptors Context triple: [Premiers Crus (Sauternes and Barsac), notableAromaDescriptors, honey]
-
A.
characteristicAroma
Indicates that one entity has a distinctive smell or scent that characterizes or is typically associated with another entity.
-
B.
notableFlavorNotes
chosen
Indicates that something is characterized by specific, distinguishable flavor notes that are especially prominent or noteworthy.
-
C.
primaryAroma
Indicates the main or most dominant scent associated with an entity, distinguishing it from secondary or background aromas.
-
D.
secondaryAroma
Indicates that an entity has a secondary or supporting aroma characteristic in addition to its primary scent.
-
E.
commonScents
Indicates that two or more entities share the same or very similar smells or fragrances.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:13 p.m.