Triple
T10259363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indulgences in the Catholic Church |
E240553
|
entity |
| Predicate | historicallyAbusedIn |
P92471
|
FINISHED |
| Object | late medieval period |
—
|
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: late medieval period | Statement: [Indulgences in the Catholic Church, historicallyAbusedIn, late medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyAbusedIn Context triple: [Indulgences in the Catholic Church, historicallyAbusedIn, late medieval period]
-
A.
periodOfAbuse
chosen
Indicates the time span during which abusive behavior occurred or was experienced.
-
B.
abuseSurvivorOf
Indicates that one entity has previously suffered abuse perpetrated by the other entity.
-
C.
typeOfAbuse
Indicates the specific kind or category of abusive behavior that one entity inflicts on another.
-
D.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
-
E.
usedViolenceAgainst
Indicates that one entity intentionally inflicted physical force or harm upon 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:32 a.m.