Triple

T5651305
Position Surface form Disambiguated ID Type / Status
Subject Gerswalde Ortsteil Rittgarten E124515 entity
Predicate hasMunicipalityKey P3943 FINISHED
Object 12073512 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: 12073512 | Statement: [Gerswalde Ortsteil Rittgarten, hasMunicipalityKey, 12073512]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMunicipalityKey
Context triple: [Gerswalde Ortsteil Rittgarten, hasMunicipalityKey, 12073512]
  • A. hasMunicipalityCode chosen
    Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
  • B. hasMunicipalityType
    Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
  • C. municipalKey
    Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
  • D. hasMemberMunicipality
    Indicates that an administrative region or governing body includes a specific municipality as one of its constituent members.
  • E. isInMunicipality
    Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
  • 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_69c00825df388190a58742fa9b1aa33d completed March 22, 2026, 3:17 p.m.
NER Named-entity recognition batch_69c022d6af9481909eaeead2a39525ce completed March 22, 2026, 5:11 p.m.
PD Predicate disambiguation batch_69c01b2274b48190b2ef57ed728f785c completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:42 p.m.