Triple
T18283196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloister Wraiths |
E437913
|
entity |
| Predicate | typicalVictims |
P36783
|
FINISHED |
| Object | intruders |
—
|
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: intruders | Statement: [Cloister Wraiths, typicalVictims, intruders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVictims Context triple: [Cloister Wraiths, typicalVictims, intruders]
-
A.
victimGroup
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
B.
victimCategory
Indicates the classification or type of victim associated with an event, action, or harmful outcome.
-
C.
mainVictims
chosen
Indicates that the related entities are the primary or principal targets harmed or affected by an action, event, or perpetrator.
-
D.
victimGroupHelped
Indicates that assistance, support, or aid was provided to a group identified as victims.
-
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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50057c5c881909fcda72f4a98c8c3 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.