Triple
T300802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Hawk |
E6193
|
entity |
| Predicate | resisted |
P437
|
FINISHED |
| Object | United States expansion into Native American lands |
—
|
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: United States expansion into Native American lands | Statement: [Black Hawk, resisted, United States expansion into Native American lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resisted Context triple: [Black Hawk, resisted, United States expansion into Native American lands]
-
A.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
C.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
D.
resolution
Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
-
E.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93aff048190a633c8ae2b76a41f |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.