Triple
T23306398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heiderhof |
E590447
|
entity |
| Predicate | hasMunicipalBorough |
P151800
|
FINISHED |
| Object | Bad Godesberg |
—
|
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: Bad Godesberg | Statement: [Heiderhof, hasMunicipalBorough, Bad Godesberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalBorough Context triple: [Heiderhof, hasMunicipalBorough, Bad Godesberg]
-
A.
hasBoroughCouncil
Indicates that an administrative area is governed or overseen by a specific borough council.
-
B.
isCountyBorough
Indicates that the subject entity has the status or classification of a county borough in relation to the object entity.
-
C.
hasMunicipalDistrict
Indicates that an administrative entity includes or is divided into one or more municipal districts as its subordinate units.
-
D.
hasMetropolitanBoroughStatus
Indicates that an administrative area holds the legal and governmental status of a metropolitan borough.
-
E.
containsMetropolitanBorough
Indicates that an administrative area includes within its boundaries one or more metropolitan boroughs as subordinate units.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972737c08190bd011776564c3861 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:05 p.m.