Triple
T11052723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haaksbergen |
E261296
|
entity |
| Predicate | municipalCouncilType |
P21035
|
FINISHED |
| Object | municipal council |
—
|
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: municipal council | Statement: [Haaksbergen, municipalCouncilType, municipal council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalCouncilType Context triple: [Haaksbergen, municipalCouncilType, municipal council]
-
A.
councilType
chosen
Indicates the specific kind or classification of a council that an entity is associated with or designated as.
-
B.
municipalWardType
Indicates the specific category or classification of a municipal ward within a local government or administrative structure.
-
C.
hasMunicipalityType
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
D.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
-
E.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7986c0df88190b29d71db5538450a |
completed | April 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.