Triple
T18682258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holzwickede |
E456761
|
entity |
| Predicate | usesMunicipalCode |
P3943
|
FINISHED |
| Object | 05978016 |
—
|
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: 05978016 | Statement: [Holzwickede, usesMunicipalCode, 05978016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMunicipalCode Context triple: [Holzwickede, usesMunicipalCode, 05978016]
-
A.
hasMunicipalityCode
chosen
Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
-
B.
municipalCodeSystem
Indicates a system that defines, organizes, or standardizes codes or regulations used by a municipality.
-
C.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
D.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
E.
usesMunicipalGovernmentAct
Indicates that an entity operates under, applies, or is governed by the provisions of a Municipal Government Act.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2906ec8190ad8db8e3ae6b2945 |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.