Triple
T2319834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauk |
E51151
|
entity |
| Predicate | historicalResistanceTo |
P18970
|
FINISHED |
| Object | U.S. expansion |
—
|
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: U.S. expansion | Statement: [Sauk, historicalResistanceTo, U.S. expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalResistanceTo Context triple: [Sauk, historicalResistanceTo, U.S. expansion]
-
A.
historicallyOpposedBy
chosen
Indicates that one entity has been the target of opposition, resistance, or antagonism from another entity over a historical period.
-
B.
historicalPower
Indicates that one entity held significant influence, control, or authority over another during a past period.
-
C.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
D.
historicalCondition
Indicates that one entity represents a condition, state, or circumstance that applied to another entity at some point in the past.
-
E.
historicallySoughtAs
Indicates that one entity has been pursued, desired, or actively sought by another entity over a historical period or in past contexts.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.