Triple
T34593854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blasewitz |
E888256
|
entity |
| Predicate | municipalityCodeLevel |
P80007
|
FINISHED |
| Object | Stadtteil |
—
|
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: Stadtteil | Statement: [Blasewitz, municipalityCodeLevel, Stadtteil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalityCodeLevel Context triple: [Blasewitz, municipalityCodeLevel, Stadtteil]
-
A.
hasMunicipalLevel
chosen
Indicates that an entity is associated with a specific level or tier within a municipal (local government) hierarchy.
-
B.
municipalCodeSystem
Indicates a system that defines, organizes, or standardizes codes or regulations used by a municipality.
-
C.
hasMunicipalLevelBelow
Indicates that one administrative unit has another, lower-level municipal unit directly subordinate to it in the hierarchy.
-
D.
hasMunicipalityCode
Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
-
E.
isProvincialLevelMunicipality
Indicates that a municipality holds the administrative status and authority of a province-level jurisdiction within a country’s governmental hierarchy.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 2:03 a.m.