Triple
T33623245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgil Sollozzo |
E861328
|
entity |
| Predicate | ordersAssassinationAttemptOn |
P104597
|
FINISHED |
| Object | Vito Corleone |
—
|
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: Vito Corleone | Statement: [Virgil Sollozzo, ordersAssassinationAttemptOn, Vito Corleone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordersAssassinationAttemptOn Context triple: [Virgil Sollozzo, ordersAssassinationAttemptOn, Vito Corleone]
-
A.
ordersAssassinationOf
chosen
Indicates that one entity commands or arranges for another entity to be killed, typically through a hired or subordinate agent.
-
B.
assassinationEvent
Indicates a deliberate killing of a specific individual, typically for political or strategic reasons, carried out as a planned event.
-
C.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
-
D.
relatedAssassination
Indicates a relationship where one entity is connected to, involved in, or associated with an assassination event concerning another entity.
-
E.
consequenceOfAssassinationAttempt
Indicates a state, event, or condition that occurs as a direct result of an assassination attempt.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:41 a.m.