Triple
T28223281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attack on William H. Seward |
E711517
|
entity |
| Predicate | attackerAlias |
P124150
|
FINISHED |
| Object | Lewis Payne |
—
|
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: Lewis Payne | Statement: [Attack on William H. Seward, attackerAlias, Lewis Payne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackerAlias Context triple: [Attack on William H. Seward, attackerAlias, Lewis Payne]
-
A.
attacker
Indicates a relationship where one entity initiates a harmful or hostile action against another entity.
-
B.
attackerSide
Indicates which party or faction is responsible for carrying out an attack in a conflict or violent incident.
-
C.
perpetratorAlias
chosen
Indicates that an entity is known or referred to by an alternative name or alias specifically in the context of being the perpetrator of an act or offense.
-
D.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
-
E.
victimAlias
Indicates that an entity is known or referred to by an alternative name specifically in the role of a victim.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643530d38819090a74ea250785b82 |
completed | May 2, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:48 p.m.