Triple
T15671885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergen op Zoom municipal council |
E377332
|
entity |
| Predicate | headOfCouncilRole |
P11005
|
FINISHED |
| Object | mayor of Bergen op Zoom |
—
|
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: mayor of Bergen op Zoom | Statement: [Bergen op Zoom municipal council, headOfCouncilRole, mayor of Bergen op Zoom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headOfCouncilRole Context triple: [Bergen op Zoom municipal council, headOfCouncilRole, mayor of Bergen op Zoom]
-
A.
roleInCouncil
chosen
Indicates that an entity holds a specific position or function within a council or governing body.
-
B.
headOfGovernmentBody
Indicates that one entity serves as the chief executive or leading official in charge of governing another entity, typically a political or administrative body.
-
C.
headOfOffice
Indicates that one entity serves as the chief or leading authority in charge of a particular office or organizational unit.
-
D.
hasCouncilLeader
Indicates that an entity has a specific person or body serving as the leader of its council.
-
E.
seatOfCouncil
Indicates that a location serves as the official meeting place or headquarters of a council.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f13b1b08190beabc9f4098aa096 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.