Triple
T32596488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean-Marie Bastien-Thiry |
E833223
|
entity |
| Predicate | plannedAssassinationTarget |
P119131
|
FINISHED |
| Object | Charles de Gaulle |
—
|
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: Charles de Gaulle | Statement: [Jean-Marie Bastien-Thiry, plannedAssassinationTarget, Charles de Gaulle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedAssassinationTarget Context triple: [Jean-Marie Bastien-Thiry, plannedAssassinationTarget, Charles de Gaulle]
-
A.
wasAssassinationTarget
chosen
Indicates that an entity was the intended victim or objective of an assassination attempt.
-
B.
assassinationOrganizedBy
Indicates that an assassination was planned, directed, or coordinated by a particular agent or organization.
-
C.
wasAssassinatedIn
Indicates that an entity was killed in a deliberate, targeted assassination that occurred at a specific place or time.
-
D.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
E.
relatedAssassination
Indicates a relationship where one entity is connected to, involved in, or associated with an assassination event concerning another 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:05 a.m.