Triple
T34615928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish regions |
E888862
|
entity |
| Predicate | abolishedPreviousLevel |
P120279
|
FINISHED |
| Object | amtskommuner (counties) |
—
|
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: amtskommuner (counties) | Statement: [Danish regions, abolishedPreviousLevel, amtskommuner (counties)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedPreviousLevel Context triple: [Danish regions, abolishedPreviousLevel, amtskommuner (counties)]
-
A.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
B.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
C.
abolishedToCreate
chosen
Indicates that one entity is formally ended, eliminated, or discontinued for the purpose of establishing or bringing into existence another entity.
-
D.
previouslyAbolished
Indicates that something was officially ended, discontinued, or annulled at some point in the past.
-
E.
wasAbolishedBy
Indicates that an institution, practice, law, or entity ceased to exist or operate as a result of an action taken by another entity.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:03 a.m.