Triple
T33728169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon Doyle |
E864201
|
entity |
| Predicate | victimOfAttackBy |
P177410
|
FINISHED |
| Object | Jacqueline de Bellefort |
—
|
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: Jacqueline de Bellefort | Statement: [Simon Doyle, victimOfAttackBy, Jacqueline de Bellefort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimOfAttackBy Context triple: [Simon Doyle, victimOfAttackBy, Jacqueline de Bellefort]
-
A.
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.
-
B.
victimWas
chosen
Indicates that one entity was the victim of an action, event, or harmful behavior carried out by another entity.
-
C.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
D.
coVictim
Indicates that two or more entities are victims in the same harmful event or incident.
-
E.
portraysAsVictim
Indicates that one entity represents or depicts another entity as a victim in a given context or narrative.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:44 a.m.