Triple

T31780340
Position Surface form Disambiguated ID Type / Status
Subject Ofwegen E811182 entity
Predicate formerMunicipalityContext P5557 FINISHED
Object Jacobswoude 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: Jacobswoude | Statement: [Ofwegen, formerMunicipalityContext, Jacobswoude]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerMunicipalityContext
Context triple: [Ofwegen, formerMunicipalityContext, Jacobswoude]
  • A. formerCityContext
    Indicates that the subject entity was formerly classified or recognized as a city within the specified contextual scope or time frame.
  • B. containsFormerMunicipality
    Indicates that an administrative unit includes within its boundaries an area that was previously an independent municipality.
  • C. formerMunicipalityOf chosen
    Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
  • D. formerMunicipalityType
    Indicates that an entity was previously classified as a specific type of municipality but no longer holds that municipal status.
  • E. previousMunicipalityNameVariant
    Indicates that an entity had a different municipality name in the past, specifying a former variant of its municipal designation.
  • 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_69f348e544a48190ab6e700b05f6438c completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69ff4de66ba481908e7184b3cf9d4d2d completed May 9, 2026, 3:08 p.m.
PD Predicate disambiguation batch_69ff4c702a5881909c6684c74807e945 completed May 9, 2026, 3:02 p.m.
Created at: April 30, 2026, 11:36 p.m.