Triple
T28588375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fieschi assassination attempt |
E723571
|
entity |
| Predicate | perpetratorInjured |
P58567
|
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, perpetratorInjured, Giuseppe Marco Fieschi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratorInjured Context triple: [Fieschi assassination attempt, perpetratorInjured, Giuseppe Marco Fieschi]
-
A.
perpetratorDeath
Indicates that the referenced individual is the one who caused or is responsible for another entity’s death.
-
B.
injuredIn
chosen
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
C.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
D.
hasInjuredPerson
Indicates that an entity has a person who has been harmed or injured associated with it.
-
E.
allegedVictimOf
Indicates that one entity is claimed or reported to have been harmed, wronged, or victimized by another entity, without asserting that the claim is proven.
- 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_69f650fb69308190ae8dbe9a897ae7b0 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cb1cf5481908a4fb19b531f52e2 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:19 a.m.