Triple
T4784036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesuit ministries |
E106432
|
entity |
| Predicate | collaboratorsInclude |
P59302
|
FINISHED |
| Object | Jesuit priests |
—
|
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: Jesuit priests | Statement: [Jesuit ministries, collaboratorsInclude, Jesuit priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaboratorsInclude Context triple: [Jesuit ministries, collaboratorsInclude, Jesuit priests]
-
A.
collaboratorName
Indicates that the predicate specifies the name of a person or entity who collaborates with another in some shared activity or project.
-
B.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
C.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
D.
primaryCollaborator
Indicates that one entity serves as the main or most significant partner working jointly with another entity on a shared activity, project, or goal.
-
E.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6922407481908565ed0b1dac2b30 |
completed | March 20, 2026, 3:34 p.m. |
Created at: March 20, 2026, 1:22 p.m.