Triple
T17617688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champagne de Venoge |
E429126
|
entity |
| Predicate | grapeSourcing |
P44919
|
FINISHED |
| Object | premier cru vineyards |
—
|
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: premier cru vineyards | Statement: [Champagne de Venoge, grapeSourcing, premier cru vineyards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapeSourcing Context triple: [Champagne de Venoge, grapeSourcing, premier cru vineyards]
-
A.
grapeSource
chosen
Indicates that one entity is the origin or provider of grapes used by another entity.
-
B.
grapeProduct
Indicates that one entity is a product derived from or made using grapes.
-
C.
grapesVinifiedAt
Indicates that grapes were processed and turned into wine at a specific location or facility.
-
D.
grapeSourceFlexibility
Indicates that the source or origin of grapes involved in a relationship or process can vary or be chosen flexibly rather than being fixed.
-
E.
grapeParentage
Indicates the parent-offspring relationship between grape varieties, specifying which grape(s) are the progenitors of another grape.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d33a2b081908deecee773c333af |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.