Triple
T30311073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act III of Tosca |
E770923
|
entity |
| Predicate | CavaradossiDeathMethod |
P48923
|
FINISHED |
| Object | 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: firing squad | Statement: [Act III of Tosca, CavaradossiDeathMethod, firing squad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CavaradossiDeathMethod Context triple: [Act III of Tosca, CavaradossiDeathMethod, firing squad]
-
A.
hasMannerOfDeath
chosen
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
B.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
-
C.
allegedMannerOfDeath
Indicates that the specified manner of death is claimed or reported for an entity, but not confirmed as factual.
-
D.
martyrdomMethod
Indicates the method or means by which an individual becomes a martyr (i.e., how the martyrdom is carried out).
-
E.
finalSinkingMethod
Indicates the method or process ultimately used to sink or deliberately submerge an object, typically a vessel or structure.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6816c17e08190b543186d578dca88 |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:50 p.m.