Triple
T5698896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zahhak |
E125608
|
entity |
| Predicate | commits |
P18480
|
FINISHED |
| Object | mass murder |
—
|
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: mass murder | Statement: [Zahhak, commits, mass murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commits Context triple: [Zahhak, commits, mass murder]
-
A.
committed
chosen
Indicates that an agent has carried out or been responsible for a specific act, event, or wrongdoing.
-
B.
commutation
Indicates the legal action of reducing, altering, or substituting a previously imposed penalty or obligation, typically making it less severe while preserving the underlying judgment or relationship.
-
C.
guaranteeCommitments
Indicates a relationship where one party formally assures that specific obligations or promises made to another party will be fulfilled or upheld.
-
D.
commutedBy
Indicates that a person or entity regularly travels to and from a place using a specified mode or means of transportation.
-
E.
commitment
Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0240ecef48190bdef10b38ecb2bd0 |
completed | March 22, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.