Triple
T36248960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Bremen |
E891741
|
entity |
| Predicate | municipalUser |
P184805
|
FINISHED |
| Object | Bremen city council |
—
|
NE NERFINISHED |
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: Bremen city council | Statement: [Coat of arms of Bremen, municipalUser, Bremen city council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalUser Context triple: [Coat of arms of Bremen, municipalUser, Bremen city council]
-
A.
municipalUse
Indicates that something is intended for, designated as, or used in connection with municipal or local government purposes.
-
B.
municipalKey
Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
-
C.
municipalScope
Indicates that something falls within the authority, jurisdiction, or functional domain of a municipality or local city government.
-
D.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
E.
servesAsMunicipalAuthorityFor
Indicates that an entity functions as the official municipal governing or administrative authority for a specified locality or jurisdiction.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5f89c5c8190825ed5d4317c540c |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.