Triple
T4784006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesuit ministries |
E106432
|
entity |
| Predicate | corePurpose |
P46456
|
FINISHED |
| Object | service of faith |
—
|
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: service of faith | Statement: [Jesuit ministries, corePurpose, service of faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corePurpose Context triple: [Jesuit ministries, corePurpose, service of faith]
-
A.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
B.
cultPurpose
chosen
Indicates that an entity (such as a cult, group, or organization) exists or operates with a specific overarching purpose, goal, or objective.
-
C.
primaryTopicOf
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
-
D.
coreIdea
Indicates the central concept or primary message that underlies or unifies something, such as a text, argument, or work.
-
E.
purposeOfWork
Indicates that one entity is the intended goal, function, or objective that motivates or justifies the work performed by another entity.
- 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_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. |
Created at: March 20, 2026, 1:22 p.m.