Triple
T34615883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kommunalreformen 2007 |
E888861
|
entity |
| Predicate | introducedEntity |
P513
|
FINISHED |
| Object | Region Hovedstaden |
—
|
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 Hovedstaden | Statement: [Kommunalreformen 2007, introducedEntity, Region Hovedstaden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedEntity Context triple: [Kommunalreformen 2007, introducedEntity, Region Hovedstaden]
-
A.
introducedForEntity
Indicates that one entity was brought into use, presented, or made known specifically for the benefit, purpose, or context of another entity.
-
B.
eraIntroduced
Indicates the historical era or time period during which something was first introduced or came into use.
-
C.
introduced
chosen
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
D.
wereIntroducedBy
Indicates that one entity became known, presented, or brought to the attention of another entity through the action or mediation of a third party.
-
E.
introducedSpecies
Indicates that a species has been brought by humans, intentionally or unintentionally, into an environment where it does not naturally occur.
- 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_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 2:03 a.m.