Triple
T9288102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourgogne Aligoté AOC |
E223447
|
entity |
| Predicate | sparklingWinePermitted |
P38388
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Bourgogne Aligoté AOC, sparklingWinePermitted, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sparklingWinePermitted Context triple: [Bourgogne Aligoté AOC, sparklingWinePermitted, false]
-
A.
sparklingWineAllowed
chosen
Indicates that the use, serving, or presence of sparkling wine is permitted in the given context or under specified conditions.
-
B.
whiteWineProductionAllowed
Indicates that producing white wine is permitted under the relevant rules, regulations, or conditions.
-
C.
roséWineAllowed
Indicates that the consumption or presence of rosé wine is permitted in the given context or under the specified conditions.
-
D.
allowsTastingOf
Indicates that one entity permits another entity to sample or try the taste of something.
-
E.
grapeVarietyAllowed
Indicates that a specific grape variety is permitted or authorized for use in a given context, such as a wine, region, or product specification.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0861425c81909e3ab11e19cc2f65 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.