Triple
T74849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erwin Rommel |
E1496
|
entity |
| Predicate | wasAccusedOf |
P873
|
FINISHED |
| Object | involvement in the 20 July plot against Hitler |
—
|
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: involvement in the 20 July plot against Hitler | Statement: [Erwin Rommel, wasAccusedOf, involvement in the 20 July plot against Hitler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAccusedOf Context triple: [Erwin Rommel, wasAccusedOf, involvement in the 20 July plot against Hitler]
-
A.
firstAccused
Indicates that the subject is the primary or earliest individual formally charged or blamed in a particular case or incident.
-
B.
accusationType
chosen
Indicates the specific category or nature of an accusation made by one party against another.
-
C.
numberOfPeopleAccused
Indicates the count of individuals who are formally alleged to have committed a particular act or offense.
-
D.
prosecuted
Indicates that legal authorities have formally brought criminal charges against an entity and pursued a case against them in a court of law.
-
E.
perpetratedBy
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a25314bd6c81908d1cfd4b83f20049 |
completed | Feb. 28, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69a24eae77ec81909015906f31f2b62e |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.