Triple
T31426774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyveke Sigbritsdatter |
E801683
|
entity |
| Predicate | allegedMurderer |
P41279
|
FINISHED |
| Object | Torben Oxe |
—
|
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: Torben Oxe | Statement: [Dyveke Sigbritsdatter, allegedMurderer, Torben Oxe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedMurderer Context triple: [Dyveke Sigbritsdatter, allegedMurderer, Torben Oxe]
-
A.
suspectedPerpetrator
Indicates that an entity is believed or alleged to be the person responsible for committing a particular harmful or illegal act.
-
B.
hasMurderer
Indicates that one entity is the person who committed the murder of another entity.
-
C.
allegedToHaveKilled
chosen
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
D.
perpetratorOfKilling
Indicates that an entity is the one who carried out or caused a particular killing.
-
E.
perpetratorInCase
Indicates that an entity is the person or group responsible for committing the offense or wrongdoing in a particular legal or investigative case.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 30, 2026, 8:53 p.m.