Triple
T7471333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cercyon |
E176511
|
entity |
| Predicate | methodOfKillingVictims |
P61208
|
FINISHED |
| Object | wrestling them to death |
—
|
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: wrestling them to death | Statement: [Cercyon, methodOfKillingVictims, wrestling them to death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfKillingVictims Context triple: [Cercyon, methodOfKillingVictims, wrestling them to death]
-
A.
numberOfVictimsKilled
Indicates the count of victims who were killed as a result of the referenced event or action.
-
B.
usedMethodOfKilling
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
C.
typeOfKilling
chosen
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
-
D.
perpetratorOfKilling
Indicates that an entity is the one who carried out or caused a particular killing.
-
E.
hasMannerOfDeathOfVictim
Indicates the specific way or circumstances in which the victim died in relation to the event or action being described.
- 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_69c69f223fd88190b4c69b95d7cbeeda |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f415b5cc81909e1e097c90f460b6 |
completed | March 27, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:41 p.m.