Triple
T13440972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbingerode (Harz) |
E320357
|
entity |
| Predicate | municipalReformDate |
P5212
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Elbingerode (Harz), municipalReformDate, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalReformDate Context triple: [Elbingerode (Harz), municipalReformDate, 2010]
-
A.
municipalityReform
Indicates a formal reorganization or restructuring of a municipality’s administrative boundaries, governance, or status.
-
B.
timeOfMajorReforms
Indicates the specific time period during which significant reforms or major changes took place.
-
C.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
-
D.
reformDate
chosen
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
E.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee704ac8190b4c7f4e0d3a88494 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.