Triple
T3159583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | alumbrados |
E66070
|
entity |
| Predicate | persecutedFor |
P33526
|
FINISHED |
| Object | suspected 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: suspected heresy | Statement: [alumbrados, persecutedFor, suspected heresy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: persecutedFor Context triple: [alumbrados, persecutedFor, suspected heresy]
-
A.
persecutedIn
Indicates that an entity is subjected to oppression, harassment, or unfair treatment within a particular place, context, or time period.
-
B.
causeOfPersecution
chosen
Indicates that one entity is the reason or basis for another entity being persecuted.
-
C.
persecutedDuring
Indicates that one entity systematically harassed, oppressed, or victimized another entity during a specified time period or event.
-
D.
methodOfPersecution
Indicates the specific means, technique, or process by which an act of persecution is carried out.
-
E.
persecutionHistory
Indicates that an entity has experienced, participated in, or is otherwise associated with acts of persecution in the past.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada61606bc8190a8ad760d680924eb |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.