Triple
T14128127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fronsac AOC |
E340086
|
entity |
| Predicate | wineTypeAllowed |
P112913
|
FINISHED |
| Object | still red wine |
—
|
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: still red wine | Statement: [Fronsac AOC, wineTypeAllowed, still red wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineTypeAllowed Context triple: [Fronsac AOC, wineTypeAllowed, still red wine]
-
A.
sparklingWineAllowed
Indicates that the use, serving, or presence of sparkling wine is permitted in the given context or under specified conditions.
-
B.
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.
-
C.
roséWineAllowed
Indicates that the consumption or presence of rosé wine is permitted in the given context or under the specified conditions.
-
D.
regulatesWineType
Indicates that one entity has authority or influence over the rules, standards, or conditions governing a particular type of wine.
-
E.
wineVariety
Indicates the specific type or variety of wine associated with an entity.
- F. None of above. chosen
Provenance (4 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6098013c8190b1bac9d3fff60acd |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.