Triple

T36757880
Position Surface form Disambiguated ID Type / Status
Subject Naustdal E908103 entity
Predicate formerMunicipalityExistedFrom P202719 FINISHED
Object 1896 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: 1896 | Statement: [Naustdal, formerMunicipalityExistedFrom, 1896]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerMunicipalityExistedFrom
Context triple: [Naustdal, formerMunicipalityExistedFrom, 1896]
  • A. formerMunicipalityOf
    Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
  • B. containsFormerMunicipality
    Indicates that an administrative unit includes within its boundaries an area that was previously an independent municipality.
  • C. formerMunicipalityDisestablished
    Indicates that a municipality, which previously existed as an administrative unit, was officially dissolved or ceased to exist at a specific point in time.
  • D. formerMunicipalityType
    Indicates that an entity was previously classified as a specific type of municipality but no longer holds that municipal status.
  • E. servedMunicipalityBeforeAmalgamation
    Indicates that an entity provided municipal services or governance to a municipality prior to its amalgamation into a larger administrative unit.
  • 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_69f76e779bec8190be0e1f87a131e0f4 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a00af6b3a948190a92813c13384c304 completed May 10, 2026, 4:16 p.m.
PD Predicate disambiguation batch_6a00aec35610819085dd5137715a4228 completed May 10, 2026, 4:13 p.m.
PDg Predicate description generation batch_6a00af6a5ffc819095c7331518a09f53 completed May 10, 2026, 4:16 p.m.
Created at: May 3, 2026, 4:12 p.m.