Triple
T22936703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sachsenhausen (Giengen an der Brenz) |
E569604
|
entity |
| Predicate | hasMayorOfMunicipality |
P185
|
FINISHED |
| Object | mayor of Giengen an der Brenz |
—
|
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 Giengen an der Brenz | Statement: [Sachsenhausen (Giengen an der Brenz), hasMayorOfMunicipality, mayor of Giengen an der Brenz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMayorOfMunicipality Context triple: [Sachsenhausen (Giengen an der Brenz), hasMayorOfMunicipality, mayor of Giengen an der Brenz]
-
A.
hasMayor
chosen
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.
hasViceMayor
Indicates that an entity holds the position of vice mayor for a given administrative or governmental body.
-
D.
hasMayorAsMember
Indicates that a group or organization includes a mayor among its members.
-
E.
hasCityManager
Indicates that an entity has a specific individual who serves in the role of city manager for it.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813608e48190922df7a5386dc391 |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.