Triple
T32251317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helleland parish |
E823890
|
entity |
| Predicate | parishNumberingAuthority |
P173884
|
FINISHED |
| Object | Church of Norway |
—
|
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: Church of Norway | Statement: [Helleland parish, parishNumberingAuthority, Church of Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishNumberingAuthority Context triple: [Helleland parish, parishNumberingAuthority, Church of Norway]
-
A.
civilParishNumber
Indicates the identifying number assigned to a specific civil parish within an administrative or geographic system.
-
B.
usesParishSystem
Indicates that an entity organizes its local governance, administration, or jurisdiction according to a parish-based system.
-
C.
isParishEquivalent
Indicates that one administrative or ecclesiastical unit is considered equivalent in status or function to a parish.
-
D.
numberOfParishes
Indicates the total count of parishes associated with a given entity.
-
E.
ecclesiasticalParishStatus
Indicates the formal ecclesiastical status or standing of a parish within a church’s organizational structure.
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc36e36c8190a8cbabe17fb627d4 |
completed | May 3, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:40 a.m.