Triple
T38078607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaintré |
E950788
|
entity |
| Predicate | neighboringWineVillagesRegion |
P20802
|
FINISHED |
| Object | Mâconnais wine villages |
—
|
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: Mâconnais wine villages | Statement: [Chaintré, neighboringWineVillagesRegion, Mâconnais wine villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringWineVillagesRegion Context triple: [Chaintré, neighboringWineVillagesRegion, Mâconnais wine villages]
-
A.
nearWineRegion
chosen
Indicates that one entity is located close to or in the vicinity of a wine-producing region.
-
B.
nearWineRegionTown
Indicates that one location is situated close to a town associated with a wine-producing region.
-
C.
wineSubregion
Indicates that one region is a subregion within a larger, defined wine-producing region.
-
D.
wineRegionHierarchy
Indicates a hierarchical relationship between wine-producing regions, where one region is contained within or subordinate to another in an official classification or geographic structure.
-
E.
wineRegionGatewayTo
Indicates that one wine region serves as an entry point or primary access route to another wine region.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:21 p.m.