Triple

T31442410
Position Surface form Disambiguated ID Type / Status
Subject Seubersdorf in der Oberpfalz E802103 entity
Predicate isInAdministrativeDistrictOfGermany P77366 FINISHED
Object Neumarkt in der Oberpfalz 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: Neumarkt in der Oberpfalz | Statement: [Seubersdorf in der Oberpfalz, isInAdministrativeDistrictOfGermany, Neumarkt in der Oberpfalz]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInAdministrativeDistrictOfGermany
Context triple: [Seubersdorf in der Oberpfalz, isInAdministrativeDistrictOfGermany, Neumarkt in der Oberpfalz]
  • A. hasLandkreis chosen
    Indicates that an entity is associated with, or belongs to, a specific administrative district (Landkreis).
  • B. isBavarianMunicipality
    Indicates that an entity functions as a municipality located within the federal state of Bavaria.
  • C. federalStateOfGermany
    Indicates that one entity is a federal state (Bundesland) that is a constituent state within the country of Germany.
  • D. locatedInPartOfGermany
    Indicates that one entity is geographically situated within a specific region or part of Germany.
  • E. administrativeDistrictOf
    Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
  • 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_69f348c5a6bc819092a557e95438976f completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a916d2e08190bafc01cba73b6469 completed May 3, 2026, 1:47 a.m.
PD Predicate disambiguation batch_69f6a7548eb48190a69b60a3c6ad53b9 completed May 3, 2026, 1:39 a.m.
Created at: April 30, 2026, 9:06 p.m.