Triple
T9900592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Anglo-Powhatan War |
E182269
|
entity |
| Predicate | deathOrCaptureOfLeader |
P22875
|
FINISHED |
| Object | capture and death of Opechancanough |
—
|
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: capture and death of Opechancanough | Statement: [Third Anglo-Powhatan War, deathOrCaptureOfLeader, capture and death of Opechancanough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathOrCaptureOfLeader Context triple: [Third Anglo-Powhatan War, deathOrCaptureOfLeader, capture and death of Opechancanough]
-
A.
leaderCapturedAndExecuted
Indicates that a leader was seized by an opposing force and subsequently put to death as a consequence of that capture.
-
B.
monarchKilledInBattle
Indicates that a monarch died as a direct result of being killed during a battle.
-
C.
diedDuringReignOf
Indicates that one entity died while another entity was in power or ruling.
-
D.
coupLeader
Indicates that the subject is the primary organizer or head figure responsible for leading a coup against an existing authority.
-
E.
fateOfLeaders
chosen
Indicates the ultimate outcome or destiny that befalls leaders, such as their end, removal, or final status.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4e0705c8190bd17e36aff615cdd |
completed | April 2, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.