Triple
T28176712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viborg County |
E715610
|
entity |
| Predicate | regionAfterReform |
P190659
|
FINISHED |
| Object | Region Midtjylland |
—
|
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: Region Midtjylland | Statement: [Viborg County, regionAfterReform, Region Midtjylland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionAfterReform Context triple: [Viborg County, regionAfterReform, Region Midtjylland]
-
A.
regionBeforeReform
Indicates that a region is defined or considered as it existed prior to a specific reform or reorganization.
-
B.
countryAfterReform
Indicates that one country entity represents the state of that country after a specified reform or transformation has taken place.
-
C.
afterReformStatus
Indicates the status or condition of an entity following a specified reform or change process.
-
D.
regionAfter1974
Indicates that the specified region is defined or recognized as it exists after the year 1974, typically reflecting post-1974 political or administrative boundaries.
-
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. 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: April 27, 2026, 10:16 p.m.