Triple
T29997002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of El Paso |
E762053
|
entity |
| Predicate | hasReligiousPersonnel |
P9815
|
FINISHED |
| Object | religious sisters |
—
|
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: religious sisters | Statement: [Roman Catholic Diocese of El Paso, hasReligiousPersonnel, religious sisters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousPersonnel Context triple: [Roman Catholic Diocese of El Paso, hasReligiousPersonnel, religious sisters]
-
A.
hasClergy
chosen
Indicates that an organization or institution possesses or is served by members of the clergy.
-
B.
hasClergyCharacter
Indicates that an entity possesses a religious or clerical role, status, or character.
-
C.
hasReligiousRoleEquivalent
Indicates that two religious roles are considered functionally or hierarchically equivalent within or across religious traditions.
-
D.
hasClericalMember
Indicates that an entity includes or is associated with a member who performs clerical or administrative duties.
-
E.
hasReligiousOffice
Indicates that an entity holds or occupies a specific religious role, position, or office within a religious organization or tradition.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0045a7b4c081908e4dedabda7cf790 |
completed | May 10, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_6a0042b148a48190974b173f352e4b7f |
completed | May 10, 2026, 8:32 a.m. |
Created at: April 29, 2026, 6:40 p.m.