Triple
T10455195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alsace AOC |
E246532
|
entity |
| Predicate | traditionalBottleType |
P64696
|
FINISHED |
| Object | flûte d’Alsace |
—
|
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: flûte d’Alsace | Statement: [Alsace AOC, traditionalBottleType, flûte d’Alsace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalBottleType Context triple: [Alsace AOC, traditionalBottleType, flûte d’Alsace]
-
A.
barrelType
Indicates the specific kind or category of barrel associated with or used in relation to an entity.
-
B.
bottleFeature
chosen
Indicates that a bottle possesses or is characterized by a particular feature or attribute.
-
C.
traditionalWineChoice
Indicates that an entity selects or prefers a wine option that aligns with customary or historically established pairing or serving practices.
-
D.
bottlingStrengthRange
Indicates the range of alcohol strengths at which a beverage is bottled.
-
E.
traditionalDrink
Indicates that one entity is a beverage customarily consumed within the culture, heritage, or longstanding practices associated with another entity.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe48d15c8190bae0d4859e6cda5d |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:18 p.m.