Triple
T38185415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sury-en-Vaux |
E1005301
|
entity |
| Predicate | wineAppellationAssociation |
P68485
|
FINISHED |
| Object | Sancerre AOC |
—
|
NE NERFINISHED |
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: Sancerre AOC | Statement: [Sury-en-Vaux, wineAppellationAssociation, Sancerre AOC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineAppellationAssociation Context triple: [Sury-en-Vaux, wineAppellationAssociation, Sancerre AOC]
-
A.
wineAppellation
chosen
Indicates that a wine originates from, and is classified under, a specific geographic appellation or designated wine-producing region.
-
B.
wineLawRegionType
Indicates the type or category of legal designation that governs wine production in a particular region.
-
C.
wineLawRegionName
Indicates that a specific name refers to the legal wine-producing region defined by wine regulations.
-
D.
wineLawRegionFocus
Indicates that a legal rule or regulation specifically concerns or targets a particular geographic region in the context of wine.
-
E.
appellationType
Indicates the specific kind or category of name or designation applied to an 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.