Triple
T20211322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood quill |
E493491
|
entity |
| Predicate | victimExperience |
P70160
|
FINISHED |
| Object | repeated carving of the same phrase |
—
|
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: repeated carving of the same phrase | Statement: [Blood quill, victimExperience, repeated carving of the same phrase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimExperience Context triple: [Blood quill, victimExperience, repeated carving of the same phrase]
-
A.
victimParticipation
Indicates that the victim took part in, contributed to, or was otherwise involved in the event or action described.
-
B.
victimSide
Indicates that one entity is on, represents, or corresponds to the side of the victim in a conflict, incident, or harmful event.
-
C.
portraysAsVictim
Indicates that one entity represents or depicts another entity as a victim in a given context or narrative.
-
D.
victimState
chosen
Indicates the condition or status that a victim is in as a result of an event, action, or harmful incident.
-
E.
victimStatus
Indicates the condition or state of a person who has been harmed or wronged as a result of an event, action, or offense.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed5691c8190bf253b1d4ee6e88f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.