Triple
T23589926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Church in Norway |
E582447
|
entity |
| Predicate | centerOfPilgrimage |
P20225
|
FINISHED |
| Object | Nidaros Cathedral |
—
|
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: Nidaros Cathedral | Statement: [Catholic Church in Norway, centerOfPilgrimage, Nidaros Cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerOfPilgrimage Context triple: [Catholic Church in Norway, centerOfPilgrimage, Nidaros Cathedral]
-
A.
pilgrimageStartingPoint
Indicates the location from which a pilgrimage journey is initiated or begins.
-
B.
isPlaceOfPilgrimageFor
Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
-
C.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
D.
isPilgrimageDestination
chosen
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
E.
pilgrimageSince
Indicates that an entity has been engaged in or committed to a pilgrimage starting from a specified point in time.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03484e4819093d5c14c891f7744 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:41 p.m.