Triple
T13798820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Hamar |
E331584
|
entity |
| Predicate | hasDeanery |
P19542
|
FINISHED |
| Object | Hamar domprosti |
E1061971
|
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: Hamar domprosti | Statement: [Diocese of Hamar, hasDeanery, Hamar domprosti]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hamar domprosti Context triple: [Diocese of Hamar, hasDeanery, Hamar domprosti]
-
A.
Hamar domprosti
chosen
Hamar domprosti is a Church of Norway deanery centered in the Hamar area, overseeing several local parishes including Hamar parish.
-
B.
Hodierna
Hodierna is an Italian surname most notably associated with the 17th-century astronomer Giovanni Battista Hodierna.
-
C.
Hamap
Hamap is a Papuan language spoken on the Alor–Pantar archipelago in eastern Indonesia.
-
D.
Hodal
Hodal is a town in the Indian state of Haryana that forms part of the culturally significant Braj region associated with the legends of Lord Krishna.
-
E.
Dromi
Dromi is a mythical chain in Norse mythology that was used in an early attempt to bind the monstrous wolf Fenrir.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ce9148190b23370f6a522ff7a |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8da594c81908cb878a8cc1b3a72 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:11 p.m.