Triple
T23081057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Oslo |
E575471
|
entity |
| Predicate | hasParishNetwork |
P150863
|
FINISHED |
| Object | network of local Lutheran parishes |
—
|
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: network of local Lutheran parishes | Statement: [Diocese of Oslo, hasParishNetwork, network of local Lutheran parishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishNetwork Context triple: [Diocese of Oslo, hasParishNetwork, network of local Lutheran parishes]
-
A.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
-
B.
haveOwnParishes
Indicates that an entity possesses or is responsible for its own distinct parishes.
-
C.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
-
D.
hasParishLife
Indicates that an entity maintains or supports organized parish-based religious and community life activities.
-
E.
hasParishHouse
Indicates that a church or parish entity possesses or is associated with a specific parish house building.
- 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_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18c67e06881908d24d6267bb49553 |
completed | April 29, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:56 p.m.