Triple

T1070337
Position Surface form Disambiguated ID Type / Status
Subject Erzhausen E23310 entity
Predicate hasLevelOfAdministrativeDivision P275 FINISHED
Object local municipality 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: local municipality | Statement: [Erzhausen, hasLevelOfAdministrativeDivision, local municipality]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLevelOfAdministrativeDivision
Context triple: [Erzhausen, hasLevelOfAdministrativeDivision, local municipality]
  • A. hasDivisionLevel chosen
    Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
  • B. hasAdministrativeArea
    Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
  • C. containsAdministrativeTerritory
    Indicates that one administrative unit geographically or jurisdictionally includes another administrative territory within its boundaries.
  • D. jurisdictionLevel
    Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
  • E. hasSubdivision
    Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
  • 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_69a493ee1f908190992b5f0d1b04459b completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b914b4908190886d6698294c6b5b completed March 1, 2026, 10:09 p.m.
PD Predicate disambiguation batch_69a4b73844708190a16c9e9824ca2fb6 completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.