Triple
T21134100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tourmakeady parish |
E520767
|
entity |
| Predicate | hasParishPriest |
P9815
|
FINISHED |
| Object | parish priest of Tourmakeady |
—
|
LITERAL 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: parish priest of Tourmakeady | Statement: [Tourmakeady parish, hasParishPriest, parish priest of Tourmakeady]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishPriest Context triple: [Tourmakeady parish, hasParishPriest, parish priest of Tourmakeady]
-
A.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
-
B.
hasClergy
chosen
Indicates that an organization or institution possesses or is served by members of the clergy.
-
C.
haveOwnParishes
Indicates that an entity possesses or is responsible for its own distinct parishes.
-
D.
hasParishJurisdiction
Indicates that one entity holds official parish-level authority or administrative control over another entity or area.
-
E.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235847948190984c7009ca7f6189 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.