Triple
T24455190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Escherndorf |
E616663
|
entity |
| Predicate | wineRegionSpeciality |
P87852
|
FINISHED |
| Object | Silvaner |
—
|
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: Silvaner | Statement: [Escherndorf, wineRegionSpeciality, Silvaner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineRegionSpeciality Context triple: [Escherndorf, wineRegionSpeciality, Silvaner]
-
A.
wineRegionSpecialization
chosen
Indicates a relationship where a wine-producing region is characterized by or particularly known for specializing in a specific type or style of wine.
-
B.
wineSpeciality
Indicates that an entity (such as a person, place, or establishment) is particularly known for, focused on, or distinguished by a specific type or aspect of wine.
-
C.
wineRegionCategory
Indicates a classification relationship where a wine region is assigned to a specific category or type of wine-producing area.
-
D.
wineSubregion
Indicates that one region is a subregion within a larger, defined wine-producing region.
-
E.
wineRegion
Indicates the geographical region or area where a particular wine is produced or originates.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298c5b510819099a92da4c100ded1 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.