Triple
T32116375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douby |
E820248
|
entity |
| Predicate | grapeAuthorized |
P37246
|
FINISHED |
| Object | Gamay Noir à Jus Blanc |
—
|
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: Gamay Noir à Jus Blanc | Statement: [Douby, grapeAuthorized, Gamay Noir à Jus Blanc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapeAuthorized Context triple: [Douby, grapeAuthorized, Gamay Noir à Jus Blanc]
-
A.
authorizedIn
Indicates that an entity has been granted official permission or legal authority to act, operate, or be valid within a specified context, domain, or jurisdiction.
-
B.
grapeConditionRequired
Indicates that a specific condition or quality of grapes is required for a related process, use, or outcome.
-
C.
authorizedAccessoryRedGrape
Indicates that an accessory or related item is officially permitted or approved in the context of red grapes.
-
D.
usesGrapeType
Indicates that one entity employs or incorporates a specific type or variety of grape in its composition, production, or process.
-
E.
grapeVarietyAllowed
chosen
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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:28 a.m.