Triple
T5207262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sack of Magdeburg |
E117541
|
entity |
| Predicate | perpetratorForce |
P698
|
FINISHED |
| Object | Imperial army |
—
|
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: Imperial army | Statement: [Sack of Magdeburg, perpetratorForce, Imperial army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratorForce Context triple: [Sack of Magdeburg, perpetratorForce, Imperial army]
-
A.
perpetratedBy
chosen
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
-
B.
perpetratorAllegiance
Indicates that the perpetrator is affiliated with, loyal to, or acting on behalf of a particular group, organization, or cause.
-
C.
perpetratorStatus
Indicates the role or condition of an individual in relation to committing or being responsible for a specific harmful or criminal act.
-
D.
perpetratorNationality
Indicates the country or nationality to which a perpetrator of an act, crime, or harmful event belongs.
-
E.
hasPerpetratorOrigin
Indicates that the origin or source of a perpetrator (such as their nationality, place of birth, or background) is associated with a particular event, action, or crime.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a4a7b7c8190af5a7149f8fe4f87 |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.