Triple
T3811953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of Boston |
E93155
|
entity |
| Predicate | sufferedCrisis |
P25894
|
FINISHED |
| Object | Catholic Church sexual abuse scandal |
—
|
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: Catholic Church sexual abuse scandal | Statement: [Archdiocese of Boston, sufferedCrisis, Catholic Church sexual abuse scandal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedCrisis Context triple: [Archdiocese of Boston, sufferedCrisis, Catholic Church sexual abuse scandal]
-
A.
majorCrisis
Indicates a severe, high-impact crisis or emergency situation affecting an entity or system.
-
B.
crisisRelatedTo
chosen
Indicates a relationship where one situation, event, or condition is connected to, associated with, or relevant to a crisis.
-
C.
majorCrisisYear
Indicates the year in which a major crisis occurred or was most prominently manifested.
-
D.
majorPoliticalCrisisEnd
Indicates the point in time or event at which a significant political crisis is considered to have concluded or been resolved.
-
E.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:16 p.m.