Triple
T24573783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toomevara |
E608041
|
entity |
| Predicate | parishIn |
P71075
|
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: [Toomevara, parishIn, Roman Catholic Diocese of Killaloe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishIn Context triple: [Toomevara, parishIn, Roman Catholic Diocese of Killaloe]
-
A.
parish
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
-
B.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
C.
parishWith
chosen
Indicates that one entity is associated with, belongs to, or is administered together with another entity as part of the same parish.
-
D.
parishesIncluded
Indicates that certain parishes are contained within, or form part of, a larger administrative, geographic, or organizational unit.
-
E.
isChristianParish
Indicates that one entity is a Christian parish, i.e., an administrative or ecclesiastical unit within a Christian church associated with a particular community or territory.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a92791988190a0dff0a6f9e770e8 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:28 a.m.