Triple
T2674268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pernand-Vergelesses |
E56419
|
entity |
| Predicate | hasVineyardClassification |
P27084
|
FINISHED |
| Object | village 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: village vineyards | Statement: [Pernand-Vergelesses, hasVineyardClassification, village vineyards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVineyardClassification Context triple: [Pernand-Vergelesses, hasVineyardClassification, village vineyards]
-
A.
hasVineyards
Indicates that one entity possesses, contains, or is associated with vineyards used for growing grapevines.
-
B.
viticulturalAreaDesignation
Indicates that a specific geographic area is officially designated or recognized for viticulture (grape growing and wine production).
-
C.
viticulturalAreaType
chosen
Indicates the specific type or classification of a viticultural area associated with an entity.
-
D.
viticulturalCharacteristic
Indicates a relationship where a specific trait, quality, or property is attributed to viticulture or grape-growing practices.
-
E.
wineGrapesCultivated
Indicates that certain grape varieties are grown or cultivated specifically for producing wine.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9b228cc819097f045b4a51d8e7c |
completed | March 7, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.