Triple
T32172897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric Brady |
E821757
|
entity |
| Predicate | followsReligionAsPriest |
P82133
|
FINISHED |
| Object | Roman Catholic Church |
—
|
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 Church | Statement: [Eric Brady, followsReligionAsPriest, Roman Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsReligionAsPriest Context triple: [Eric Brady, followsReligionAsPriest, Roman Catholic Church]
-
A.
priests
Indicates that the subject serves in a religious or spiritual officiating role, typically performing sacred rituals or duties for a faith community.
-
B.
clergyMayBe
Indicates that an individual is permitted or eligible to serve in a clergy role.
-
C.
memberOfClergy
chosen
Indicates that one entity serves in an official religious or clerical role within a religious organization or institution.
-
D.
servedAsPriestDuring
Indicates that a person held and performed the role or office of a priest during a specified time period or event.
-
E.
clergy
Indicates that an entity serves in an official religious or spiritual leadership role within an organized faith or religious institution.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 1, 2026, 12:33 a.m.