Triple
T15307457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singen |
E365939
|
entity |
| Predicate | municipalWebsite |
P30293
|
FINISHED |
| Object | https://www.singen.de |
—
|
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: https://www.singen.de | Statement: [Singen, municipalWebsite, https://www.singen.de]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalWebsite Context triple: [Singen, municipalWebsite, https://www.singen.de]
-
A.
hasLocalGovernmentWebsite
chosen
Indicates that an entity has an official website specifically for its local government or municipal administration.
-
B.
governingBodyWebsite
Indicates the official website associated with the governing body responsible for an entity.
-
C.
cityGovernment
Indicates that a city’s governing authority has jurisdiction, control, or administrative responsibility over the referenced entity.
-
D.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
E.
municipalRepresentation
Indicates that one entity serves as the official municipal-level representative or governing body for another entity within a specific locality or jurisdiction.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd001b48190bbdd69337efdb907 |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.