Triple
T38419088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werkendam (historical municipality) |
E903177
|
entity |
| Predicate | hadMayorTitle |
P190859
|
FINISHED |
| Object | burgemeester |
—
|
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: burgemeester | Statement: [Werkendam (historical municipality), hadMayorTitle, burgemeester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMayorTitle Context triple: [Werkendam (historical municipality), hadMayorTitle, burgemeester]
-
A.
hasMayor
Indicates that one entity serves as the mayor of another entity, typically a city, town, or municipality.
-
B.
hasMayorOffice
Indicates that a particular entity serves as the office or official position held by a mayor of another entity.
-
C.
hasNotableMayor
Indicates that an entity has or had a mayor who is particularly distinguished, prominent, or noteworthy.
-
D.
hasMayorTerm
Indicates that a specified individual holds or has held the office of mayor for a particular jurisdiction during a defined term.
-
E.
formerMayor
Indicates that the subject once held the position of mayor of the object entity but no longer does.
- F. None of above. chosen
Provenance (4 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.