Triple
T4096978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter Rising |
E87843
|
entity |
| Predicate | executions |
P19112
|
FINISHED |
| Object | execution of 15 leaders by firing squad |
—
|
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: execution of 15 leaders by firing squad | Statement: [Easter Rising, executions, execution of 15 leaders by firing squad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executions Context triple: [Easter Rising, executions, execution of 15 leaders by firing squad]
-
A.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of another entity.
-
B.
executioner
Indicates that one entity performs or is responsible for carrying out an execution on another entity.
-
C.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
D.
conducts
Indicates that an entity organizes, directs, or carries out an activity, operation, or process involving another entity.
-
E.
numberOfExecutions
chosen
Indicates the count of times a particular action, process, or event has been carried out.
- 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_69aed94564cc8190a9c1457daedb6e7f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcdef11081908c626a89f2c0e121 |
completed | March 9, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69aef90b2ef08190ae84febfd69dd48b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.