Triple

T31175250
Position Surface form Disambiguated ID Type / Status
Subject Nandlstadt E794725 entity
Predicate isInWineOrBeerRegion P171217 FINISHED
Object German hop-growing region 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: German hop-growing region | Statement: [Nandlstadt, isInWineOrBeerRegion, German hop-growing region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInWineOrBeerRegion
Context triple: [Nandlstadt, isInWineOrBeerRegion, German hop-growing region]
  • A. isInWineOrSpiritsRegion
    Indicates that one entity (typically a location or product) is situated within or associated with a designated wine or spirits-producing region of another entity.
  • B. includesWineProvince
    Indicates that one entity (typically a region or collection) contains or encompasses a specific wine-producing province within its scope.
  • C. passesThroughWineRegion
    Indicates that something (such as a route, path, or boundary) traverses or goes through a geographic area recognized as a wine-producing region.
  • D. wineLawRegionType
    Indicates the type or category of legal designation that governs wine production in a particular region.
  • E. wineRegion
    Indicates the geographical region or area where a particular wine is produced or originates.
  • F. None of above. chosen

Provenance (4 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_69f224d5b9708190b6ca79ad2fd3a28a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69c6f01e881908fa84f5d429d37ae completed May 3, 2026, 12:53 a.m.
PD Predicate disambiguation batch_69f69665cd9c819088c388fc82fec42e completed May 3, 2026, 12:27 a.m.
PDg Predicate description generation batch_69f69c2127088190ae92c72461576d3b completed May 3, 2026, 12:51 a.m.
Created at: April 29, 2026, 9:07 p.m.