Triple
T24386525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sixmilebridge |
E614763
|
entity |
| Predicate | parishDiocese |
P2740
|
FINISHED |
| Object | Roman Catholic Diocese of Killaloe |
—
|
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: Roman Catholic Diocese of Killaloe | Statement: [Sixmilebridge, parishDiocese, Roman Catholic Diocese of Killaloe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishDiocese Context triple: [Sixmilebridge, parishDiocese, Roman Catholic Diocese of Killaloe]
-
A.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
-
B.
diocese
chosen
Indicates that one entity serves as the ecclesiastical district or jurisdiction under the authority of a bishop to which the other entity is related or belongs.
-
C.
linkedDiocese
Indicates a formal association or connection established between one diocese and another.
-
D.
parish
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
-
E.
dioceseBishop
Indicates that a person serves as the bishop (ecclesiastical leader) of a specified diocese.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29454c36c8190b7820dbf5af7b695 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.