Triple
T24966156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diedesfeld |
E624748
|
entity |
| Predicate | hasLocalMayor |
P185
|
FINISHED |
| Object | Ortsvorsteher von Diedesfeld |
—
|
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: Ortsvorsteher von Diedesfeld | Statement: [Diedesfeld, hasLocalMayor, Ortsvorsteher von Diedesfeld]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalMayor Context triple: [Diedesfeld, hasLocalMayor, Ortsvorsteher von Diedesfeld]
-
A.
hasMayor
chosen
Indicates that one entity serves as the mayor of another entity, typically a city, town, or municipality.
-
B.
hasCityManager
Indicates that an entity has a specific individual who serves in the role of city manager for it.
-
C.
hasHeadOfLocalGovernment
Indicates that an administrative area is associated with the person who serves as its chief local government official.
-
D.
hasMayorOffice
Indicates that a particular entity serves as the office or official position held by a mayor of another entity.
-
E.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 6 a.m.