Triple
T35754493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvernes parish |
E1033405
|
entity |
| Predicate | usesChurch |
P15000
|
FINISHED |
| Object | Kvernes Church |
—
|
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: Kvernes Church | Statement: [Kvernes parish, usesChurch, Kvernes Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChurch Context triple: [Kvernes parish, usesChurch, Kvernes Church]
-
A.
hasChurch
chosen
Indicates that a place or entity possesses, contains, or is associated with a church.
-
B.
withinChurch
Indicates that one entity is located inside or contained within a church.
-
C.
principalChurchOf
Indicates that one church serves as the main or most important church associated with a particular entity, such as a region, denomination, or institution.
-
D.
particularChurch
Indicates that one entity is a specific, individual church associated with or belonging to another entity (such as a denomination, region, or organization).
-
E.
motherChurch
Indicates that one church serves as the primary, founding, or supervising church in relation to another church.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:06 p.m.