Triple

T24362292
Position Surface form Disambiguated ID Type / Status
Subject Schwebheim E614094 entity
Predicate locatedInNorthernGermanyRegion P155919 FINISHED
Object Southern Germany (northern Bavaria) 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: Southern Germany (northern Bavaria) | Statement: [Schwebheim, locatedInNorthernGermanyRegion, Southern Germany (northern Bavaria)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInNorthernGermanyRegion
Context triple: [Schwebheim, locatedInNorthernGermanyRegion, Southern Germany (northern Bavaria)]
  • A. locatedInPartOfGermany
    Indicates that one entity is geographically situated within a specific region or part of Germany.
  • B. locatedInNorthernEurope
    Indicates that the subject is geographically situated within the region of Northern Europe.
  • C. locatedInFormerEastGermany
    Indicates that the subject is geographically situated within the territory that constituted East Germany before German reunification.
  • D. isLocatedInFranconiaRegion
    Indicates that something is situated within the geographical boundaries of the Franconia region.
  • E. containsGermanSpeakingArea
    Indicates that one entity geographically includes an area where German is predominantly spoken.
  • 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_69e2d7dfe7f08190b7a1f3a36483ab05 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f29385d0d48190b04154fcc3efe49a completed April 29, 2026, 11:25 p.m.
PD Predicate disambiguation batch_69f287bb1b2c81909c2e7fcc392ad143 completed April 29, 2026, 10:35 p.m.
PDg Predicate description generation batch_69f28f4d978c81908310c01def2514cc completed April 29, 2026, 11:07 p.m.
Created at: April 18, 2026, 2 a.m.