Triple
T9261660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irena Sendler |
E222592
|
entity |
| Predicate | subjectedTo |
P35270
|
FINISHED |
| Object | torture |
—
|
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: torture | Statement: [Irena Sendler, subjectedTo, torture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectedTo Context triple: [Irena Sendler, subjectedTo, torture]
-
A.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
B.
susceptibleTo
Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
-
C.
subjectOfExecution
Indicates that one entity is the object or target upon which an execution (carrying out of a death sentence) is performed by another entity.
-
D.
decisionsSubjectTo
Indicates that certain decisions are constrained by, dependent on, or must comply with specified conditions, approvals, or oversight.
-
E.
hasBeenSubjectOf
chosen
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
- 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_69ca841f2e808190a64f4c31903a1332 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07175be881908a917573ec9b9081 |
completed | April 1, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.