Triple
T883864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaw Nation |
E19085
|
entity |
| Predicate | forcedRemoval |
P16758
|
FINISHED |
| Object | relocated from Kansas to Indian Territory |
—
|
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: relocated from Kansas to Indian Territory | Statement: [Kaw Nation, forcedRemoval, relocated from Kansas to Indian Territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedRemoval Context triple: [Kaw Nation, forcedRemoval, relocated from Kansas to Indian Territory]
-
A.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
B.
removalMechanism
Indicates the method or process by which something is removed, eliminated, or taken away from a system or context.
-
C.
removedFrom
chosen
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
D.
canBeRemovedBy
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
-
E.
forcedToRetire
Indicates that an entity was compelled, rather than choosing voluntarily, to end their professional role or career.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8eca748190b58e0f08b30fba43 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.