Triple
T34598687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sør-Aurdal |
E888393
|
entity |
| Predicate | hasStaveChurch |
P15000
|
FINISHED |
| Object | Hedalen Stave Church |
E1100170
|
NE 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: Hedalen Stave Church | Statement: [Sør-Aurdal, hasStaveChurch, Hedalen Stave Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStaveChurch Context triple: [Sør-Aurdal, hasStaveChurch, Hedalen Stave Church]
-
A.
hasLiturgicalChurch
Indicates that one entity is associated with, served by, or belongs to a particular liturgical church as its religious institution.
-
B.
hasChurch
chosen
Indicates that a place or entity possesses, contains, or is associated with a church.
-
C.
hasPilgrimageChurch
Indicates that a location or entity possesses or is associated with a church that serves as a destination for religious pilgrimage.
-
D.
isMetropolitanChurch
Indicates that a church holds metropolitan status, serving as the principal ecclesiastical authority over other churches within a defined region or province.
-
E.
isOrthodoxCathedral
Indicates that the subject is a cathedral belonging to the Orthodox Christian tradition.
- F. None of above.
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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37792fcaf081909c0832ac0201249e |
completed | June 21, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: May 1, 2026, 2:03 a.m.