Triple
T8106855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uppsala Cathedral |
E189247
|
entity |
| Predicate | dedicatedTo |
P500
|
FINISHED |
| Object | Saint Eric |
E167663
|
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: Saint Eric | Statement: [Uppsala Cathedral, dedicatedTo, Saint Eric]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saint Eric Context triple: [Uppsala Cathedral, dedicatedTo, Saint Eric]
-
A.
Erik
chosen
Erik is a masculine given name of Scandinavian origin that is widely used across various European countries.
-
B.
Gunnar
Gunnar is a masculine given name of Old Norse origin, commonly used in Scandinavian countries and associated with warriors or bold fighters.
-
C.
Rigmor
Rigmor is a feminine given name of Scandinavian origin, particularly used in Norway and Denmark.
-
D.
Godric
Godric is a 1980 historical novel by Frederick Buechner that fictionalizes the life and spiritual journey of the medieval English saint Godric of Finchale.
-
E.
Ivar
Ivar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42f89dd481908f1a25e4b16a8fc8 |
completed | March 31, 2026, 3:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc94198fdc8190bcf3c6285e52fdd3 |
completed | April 1, 2026, 3:42 a.m. |
Created at: March 30, 2026, 5:31 p.m.