Triple
T16526117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Silent World of Nicholas Quinn |
E401441
|
entity |
| Predicate | victimCharacteristic |
P58515
|
FINISHED |
| Object | deaf |
—
|
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: deaf | Statement: [The Silent World of Nicholas Quinn, victimCharacteristic, deaf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimCharacteristic Context triple: [The Silent World of Nicholas Quinn, victimCharacteristic, deaf]
-
A.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
-
B.
victimAge
Indicates the age of the person who is the victim in the described event or situation.
-
C.
victimStatus
chosen
Indicates the condition or state of a person who has been harmed or wronged as a result of an event, action, or offense.
-
D.
victimGroup
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
E.
victimGroupContext
Indicates the contextual circumstances or setting in which a victim group is targeted, affected, or involved in an event or action.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed3f0388190a9f03473c37dfc46 |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.