Triple
T37244253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergheim |
E923803
|
entity |
| Predicate | municipalKey_Gemeindeschlüssel |
P180512
|
FINISHED |
| Object | 05362008 |
—
|
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: 05362008 | Statement: [Bergheim, municipalKey_Gemeindeschlüssel, 05362008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalKey_Gemeindeschlüssel Context triple: [Bergheim, municipalKey_Gemeindeschlüssel, 05362008]
-
A.
hasGermanMunicipalityKey
chosen
Indicates that an entity is associated with a specific official German municipality key (Amtlicher Gemeindeschlüssel) identifying its municipality.
-
B.
isBavarianMunicipality
Indicates that an entity functions as a municipality located within the federal state of Bavaria.
-
C.
municipalKey
Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
-
D.
cantonCode
Indicates the specific administrative canton identifier associated with an entity or location.
-
E.
mainMunicipality
Indicates that one municipality serves as the primary or central administrative municipality associated with another entity or area.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.