Triple
T19093626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Innocents |
E467350
|
entity |
| Predicate | killedBecauseOf |
P134344
|
FINISHED |
| Object | attempt to kill the newborn Jesus |
—
|
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: attempt to kill the newborn Jesus | Statement: [Holy Innocents, killedBecauseOf, attempt to kill the newborn Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killedBecauseOf Context triple: [Holy Innocents, killedBecauseOf, attempt to kill the newborn Jesus]
-
A.
killedBy
Indicates that one entity caused the death of another entity.
-
B.
killedDuring
Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
-
C.
killedOnBehalfOf
Indicates that one entity carried out a killing as a representative of, or in service to, another entity.
-
D.
requestedToBeKilledBy
Indicates that one entity has asked another entity to kill them.
-
E.
killedAlongWith
Indicates that one entity was killed at the same time and in the same event or circumstance as another entity.
- F. None of above. chosen
Provenance (4 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34cf5e481908e1f180dacd5602f |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.