Triple
T14612308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Index of Prohibited Books (Spanish Inquisition) |
E342991
|
entity |
| Predicate | reasonForProhibition |
P25587
|
FINISHED |
| Object | heresy |
—
|
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: heresy | Statement: [Index of Prohibited Books (Spanish Inquisition), reasonForProhibition, heresy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForProhibition Context triple: [Index of Prohibited Books (Spanish Inquisition), reasonForProhibition, heresy]
-
A.
reasonForBan
chosen
Indicates the justification or cause that led to an entity being banned.
-
B.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
C.
reasonForDisqualification
Indicates the specific cause or justification for which an entity was deemed ineligible or disqualified from consideration or participation.
-
D.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
E.
reasonForSanctions
Indicates the underlying cause or justification for imposing sanctions on an 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb450e6588190a94488d8e71888c8 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.