Triple
T6171203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alsace Varietals Festival |
E137699
|
entity |
| Predicate | styleEmphasis |
P17414
|
FINISHED |
| Object | cool-climate white 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: cool-climate white wines | Statement: [Alsace Varietals Festival, styleEmphasis, cool-climate white wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleEmphasis Context triple: [Alsace Varietals Festival, styleEmphasis, cool-climate white wines]
-
A.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
B.
characterStyle
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
-
C.
designEmphasizes
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
-
D.
styleLanguage
Indicates a relationship where one entity specifies the language or linguistic style in which another entity is expressed, formatted, or presented.
-
E.
editingStyle
Indicates the characteristic manner or approach used when revising, arranging, or refining content.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d910c3c8190ae6af548259295ff |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.