Triple
T26771688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Kildare and Leighlin |
E675094
|
entity |
| Predicate | hasFormerSee |
P143563
|
FINISHED |
| Object | Diocese of Kildare |
—
|
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: Diocese of Kildare | Statement: [Roman Catholic Diocese of Kildare and Leighlin, hasFormerSee, Diocese of Kildare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerSee Context triple: [Roman Catholic Diocese of Kildare and Leighlin, hasFormerSee, Diocese of Kildare]
-
A.
hasSee
Indicates that one entity has perceived or visually observed another entity.
-
B.
hasHistoricalSee
chosen
Indicates that one entity historically served as the episcopal see or central seat of authority for another entity, typically a diocese or bishopric.
-
C.
hasFormerEntity
Indicates that one entity previously existed in a different form, role, or identity that is represented by another entity.
-
D.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
-
E.
usesFormerRouteOf
Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 4:02 a.m.