Triple
T20823977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Østerlars Parish |
E512646
|
entity |
| Predicate | typeOfLocalDivision |
P15261
|
FINISHED |
| Object | parish in Denmark |
—
|
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: parish in Denmark | Statement: [Østerlars Parish, typeOfLocalDivision, parish in Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLocalDivision Context triple: [Østerlars Parish, typeOfLocalDivision, parish in Denmark]
-
A.
typeOfDistrict
Indicates the specific category or classification to which a given district belongs.
-
B.
censusDivisionType
Indicates the classification of a census division according to its official administrative or statistical type.
-
C.
localGovernmentAreaType
Indicates the specific classification or category of a local government area within an administrative or governmental hierarchy.
-
D.
typeOfDivision
chosen
Indicates the specific category or kind of division that characterizes how something is separated, organized, or partitioned.
-
E.
municipalWardType
Indicates the specific category or classification of a municipal ward within a local government or administrative structure.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2fc0cd081909e264cda686579ea |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.