Triple
T28588378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fieschi assassination attempt |
E723571
|
entity |
| Predicate | perpetratorExecuted |
P100563
|
FINISHED |
| Object | Giuseppe Marco Fieschi |
—
|
NE NERFINISHED |
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: Giuseppe Marco Fieschi | Statement: [Fieschi assassination attempt, perpetratorExecuted, Giuseppe Marco Fieschi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratorExecuted Context triple: [Fieschi assassination attempt, perpetratorExecuted, Giuseppe Marco Fieschi]
-
A.
primaryPerpetratorExecutionDate
Indicates the date on which the main perpetrator of an act or crime was executed.
-
B.
notablePrisonerExecuted
Indicates that a person, recognized as a notable or significant prisoner, was executed while in custody.
-
C.
hasNotablePersonExecuted
chosen
Indicates that a notable or prominent person has been subjected to execution (e.g., capital punishment) in relation to the referenced entity.
-
D.
victimOfExecutionBy
Indicates that one entity was executed as a result of an execution carried out by another entity.
-
E.
deathPenaltyImposed
Indicates that a legal authority has formally assigned the death penalty as the punishment for an entity.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 4:19 a.m.