Triple

T30830315
Position Surface form Disambiguated ID Type / Status
Subject Landkreis E785197 entity
Predicate locatedInAdministrativeHierarchyBetween P157112 FINISHED
Object Gemeinde 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: Gemeinde | Statement: [Landkreis, locatedInAdministrativeHierarchyBetween, Gemeinde]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInAdministrativeHierarchyBetween
Context triple: [Landkreis, locatedInAdministrativeHierarchyBetween, Gemeinde]
  • A. locatedBetween
    Indicates that one entity is positioned spatially between two other reference entities.
  • B. levelInAdministrativeHierarchy chosen
    Indicates the relative position or rank of an administrative unit within a broader hierarchical administrative structure.
  • C. isLocatedInAdministrativeArea
    Indicates that one entity is situated within the geographic or jurisdictional boundaries of a specified administrative area (such as a city, county, state, or region).
  • D. containsAdministrativeTerritory
    Indicates that one administrative unit geographically or jurisdictionally includes another administrative territory within its boundaries.
  • E. governsBetween
    Indicates a governing or regulatory relationship that exists specifically between two entities, often mediating or constraining their interaction.
  • 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_69f224b6642481909e8d701de2cd1a53 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_6a0120f070b081909b6d1a3d8ee6b80e completed May 11, 2026, 12:21 a.m.
PD Predicate disambiguation batch_6a01209da37481909683e38f264b15ef completed May 11, 2026, 12:19 a.m.
Created at: April 29, 2026, 8:44 p.m.