Triple
T7955798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocumtuck people |
E184732
|
entity |
| Predicate | decimatedBy |
P21041
|
FINISHED |
| Object | 17th-century warfare |
—
|
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: 17th-century warfare | Statement: [Pocumtuck people, decimatedBy, 17th-century warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decimatedBy Context triple: [Pocumtuck people, decimatedBy, 17th-century warfare]
-
A.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
-
B.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
-
C.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
D.
reducedPopulationOf
chosen
Indicates a relationship where one entity has caused a decrease in the size or number of individuals in a population of another entity.
-
E.
destroysFractionOf
Indicates that one entity damages or eliminates a specified fraction or proportion of another 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b60e9508190ad9974ad551bcbc6 |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:11 p.m.