Triple
T8027069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Copenhagen |
E186880
|
entity |
| Predicate | typeOfDistrict |
P80652
|
FINISHED |
| Object | ecclesiastical district |
—
|
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: ecclesiastical district | Statement: [Diocese of Copenhagen, typeOfDistrict, ecclesiastical district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDistrict Context triple: [Diocese of Copenhagen, typeOfDistrict, ecclesiastical district]
-
A.
electoralDistrictType
Indicates the specific category or kind of electoral district associated with an entity (e.g., federal, state, local).
-
B.
typeOfSpecialDistrict
Indicates the specific category or classification of a special district to which an entity belongs.
-
C.
cityDistrictType
Indicates the type or classification of a city district within an urban or administrative structure.
-
D.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
-
E.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ecb00648190bb3144acf3492bb3 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:21 p.m.