Triple
T13049259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourgogne Épineuil AOC |
E327405
|
entity |
| Predicate | styleProfile |
P106662
|
FINISHED |
| Object | light to medium-bodied red wines |
—
|
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: light to medium-bodied red wines | Statement: [Bourgogne Épineuil AOC, styleProfile, light to medium-bodied red wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleProfile Context triple: [Bourgogne Épineuil AOC, styleProfile, light to medium-bodied red wines]
-
A.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
B.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
-
C.
styleCategory
Indicates the stylistic classification or genre category that an item, work, or entity belongs to.
-
D.
styleDetail
chosen
Indicates a relationship where specific stylistic characteristics or attributes of something are described or specified in detail.
-
E.
styleInFull
Indicates that something is presented, written, or expressed in its complete, unabbreviated, or fully detailed form.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:57 p.m.