Triple
T15518780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS personnel of Buchenwald |
E368898
|
entity |
| Predicate | someMembersConvictedOf |
P118959
|
FINISHED |
| Object | murder |
—
|
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: murder | Statement: [SS personnel of Buchenwald, someMembersConvictedOf, murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: someMembersConvictedOf Context triple: [SS personnel of Buchenwald, someMembersConvictedOf, murder]
-
A.
convictedOf
Indicates that a person or entity has been found guilty of committing a specified offense or crime through a formal legal process.
-
B.
convictedIndividual
Indicates that an individual has been found guilty of a crime or offense through a formal legal process and has received a conviction.
-
C.
numberOfConvictions
Indicates the count of times an entity has been formally found guilty of an offense.
-
D.
membersArrestedIn
Indicates that certain members of a group or organization were arrested in a specified location or during a particular event or operation.
-
E.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
- F. None of above. chosen
Provenance (4 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e040343d9c8190a7d1f197c108bd9d |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 4:04 a.m.