Triple
T32890913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipality of Faxe |
E841327
|
entity |
| Predicate | formedByMunicipalReform |
P117243
|
FINISHED |
| Object | 2007 Danish Municipal Reform |
—
|
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: 2007 Danish Municipal Reform | Statement: [Municipality of Faxe, formedByMunicipalReform, 2007 Danish Municipal Reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedByMunicipalReform Context triple: [Municipality of Faxe, formedByMunicipalReform, 2007 Danish Municipal Reform]
-
A.
municipalityReform
Indicates a formal reorganization or restructuring of a municipality’s administrative boundaries, governance, or status.
-
B.
partOfAdministrativeDivisionReform
chosen
Indicates that an entity is involved in, or results from, a reorganization or restructuring of administrative divisions.
-
C.
reconstitutedAsMunicipality
Indicates that an entity which previously lost or changed its municipal status has been formally re-established or reorganized as a municipality.
-
D.
regionAfterReform
Indicates that one region is the successor or resulting region of another after an administrative or political reform.
-
E.
lastReform
Indicates the most recent reform or change that was applied to an entity, typically linking the entity to its latest reform event or version.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: May 1, 2026, 1:18 a.m.