Triple
T19354588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Boxmeer |
E484107
|
entity |
| Predicate | hadMunicipalCode |
P3943
|
FINISHED |
| Object | 0756 |
—
|
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: 0756 | Statement: [municipality of Boxmeer, hadMunicipalCode, 0756]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMunicipalCode Context triple: [municipality of Boxmeer, hadMunicipalCode, 0756]
-
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.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
D.
municipalKey
Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
-
E.
hasMunicipalPart
Indicates that an administrative or territorial entity includes a municipality as one of its constituent parts.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6190794188190a94de464d985b5fd |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.