Triple
T4578619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father General |
E101799
|
entity |
| Predicate | religiousVowsContext |
P20285
|
FINISHED |
| Object | Jesuit professed religious |
—
|
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 professed religious | Statement: [Father General, religiousVowsContext, Jesuit professed religious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousVowsContext Context triple: [Father General, religiousVowsContext, Jesuit professed religious]
-
A.
tookReligiousVows
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
B.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
C.
religiousStatus
Indicates the religious affiliation, role, or standing that an entity holds within a religious context.
-
D.
religiousOrderAssociation
chosen
Indicates that an entity is formally connected to, affiliated with, or a member of a particular religious order.
-
E.
religiousOrderSupported
Indicates that one entity provides support—such as resources, endorsement, or maintenance—to a particular religious order.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd58e2a1808190be4582d5b3003d6c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.