Triple
T30862506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberwaltersdorf |
E786098
|
entity |
| Predicate | isWineGrowingArea |
P32878
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oberwaltersdorf, isWineGrowingArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWineGrowingArea Context triple: [Oberwaltersdorf, isWineGrowingArea, true]
-
A.
viticulturalAreaCode
Indicates the designated code that identifies the specific viticultural (wine-producing) area associated with an entity.
-
B.
viticulturalAreaDesignation
chosen
Indicates that a specific geographic area is officially designated or recognized for viticulture (grape growing and wine production).
-
C.
hasWinemakingFacility
Indicates that an entity possesses or is associated with a facility where winemaking activities are carried out.
-
D.
hasVineyardsNear
Indicates that one entity possesses or is associated with vineyards located in close geographic proximity to another entity.
-
E.
hasVineyards
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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691aa2ad48190b80eff3be46cdf1e |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:47 p.m.