Triple
T38218580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheingau wine region |
E1010748
|
entity |
| Predicate | famousVineyard |
P25137
|
FINISHED |
| Object | Schloss Johannisberg |
—
|
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: Schloss Johannisberg | Statement: [Rheingau wine region, famousVineyard, Schloss Johannisberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousVineyard Context triple: [Rheingau wine region, famousVineyard, Schloss Johannisberg]
-
A.
vineyardName
Indicates the specific name assigned to a vineyard in the relationship.
-
B.
famousVintagesInclude
Indicates that certain specific vintages are recognized and listed as notable or renowned examples within a broader collection or category.
-
C.
notableWinemaker
Indicates that the subject is recognized as a distinguished or prominent winemaker.
-
D.
architectOfWinery
Indicates that an entity served as the architect responsible for designing or planning a particular winery.
-
E.
hasVineyards
chosen
Indicates that one entity possesses, contains, or is associated with vineyards used for growing grapevines.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
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:30 p.m.