Triple
T37784061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Kilmore |
E941903
|
entity |
| Predicate | hasSeminaryHistorically |
P202640
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Diocese of Kilmore, hasSeminaryHistorically, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeminaryHistorically Context triple: [Diocese of Kilmore, hasSeminaryHistorically, yes]
-
A.
hasSeminaryFormationThrough
Indicates that one entity has received or undergone seminary training, education, or formation by means of, or via the involvement of, another entity.
-
B.
hasMajorSeminary
Indicates that an institution or entity possesses or is associated with a major seminary for advanced clerical or theological training.
-
C.
seminaryFounded
Indicates that a particular entity established or created a seminary.
-
D.
hasMainSeminaryLocation
Indicates that an entity’s primary seminary is located at a specified place.
-
E.
hasMinorSeminary
Indicates that an entity operates, is associated with, or possesses a minor seminary as part of its organizational structure or activities.
- F. None of above. chosen
Provenance (4 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00a2f0d1588190a936ea7df0ef0464 |
completed | May 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_6a00a28ccd94819085b5e123f5a4769e |
completed | May 10, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_6a00a2f0207c81908eaaff8c2a0b3f97 |
completed | May 10, 2026, 3:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.