Triple
T24217611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Reykjavík |
E601348
|
entity |
| Predicate | isOnlyCatholicDioceseIn |
P110044
|
FINISHED |
| Object | Iceland |
—
|
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: Iceland | Statement: [Diocese of Reykjavík, isOnlyCatholicDioceseIn, Iceland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnlyCatholicDioceseIn Context triple: [Diocese of Reykjavík, isOnlyCatholicDioceseIn, Iceland]
-
A.
isOnlyDioceseIn
Indicates that a diocese is the sole diocese within a specified territorial or organizational jurisdiction.
-
B.
isOnlyLatinDioceseIn
chosen
Indicates that a diocese is the sole Latin-rite Catholic diocese within a specified geographic area or jurisdiction.
-
C.
isOnlyEpiscopalDioceseIn
Indicates that an episcopal diocese is the sole diocese of its kind within a specified geographic or organizational area.
-
D.
hasCatholicDiocese
Indicates that a specified place or region falls under the jurisdiction of a particular Catholic diocese.
-
E.
hasDioceseEquivalent
Indicates that an entity possesses a jurisdictional unit that is functionally equivalent to a diocese, even if it has a different formal designation.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820a80ec8190bd11f08f7733843d |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:58 p.m.