Triple
T2674258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pernand-Vergelesses |
E56419
|
entity |
| Predicate | appellationEstablished |
P32878
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [Pernand-Vergelesses, appellationEstablished, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appellationEstablished Context triple: [Pernand-Vergelesses, appellationEstablished, 1930s]
-
A.
appellationType
Indicates the specific kind or category of name or designation applied to an entity.
-
B.
notableAppellation
Indicates that an entity is known by, or commonly referred to with, a particular notable name or title.
-
C.
hasGrandCru
Indicates that an entity possesses, is associated with, or includes a wine classified as Grand Cru.
-
D.
viticulturalAreaDesignation
chosen
Indicates that a specific geographic area is officially designated or recognized for viticulture (grape growing and wine production).
-
E.
denominationOfOrigin
Indicates a legally recognized origin relationship where a product’s quality or characteristics are specifically attributable to being produced in a particular geographic 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_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.