Triple
T3808285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauk |
E93064
|
entity |
| Predicate | displacementCause |
P51873
|
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, displacementCause, U.S. expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementCause Context triple: [Sauk, displacementCause, U.S. expansion]
-
A.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
B.
displacementCategory
Indicates the type or classification of a displacement event or condition associated with an entity.
-
C.
displacementVariant
Indicates a relationship where one entity is an alternative or modified form of another that differs specifically in its spatial position or displacement.
-
D.
displacedBy
Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
-
E.
displacementClass
Indicates the category or type of physical displacement associated with an entity or event, typically grouping similar kinds or magnitudes of movement into a common class.
- F. None of above. chosen
Provenance (4 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:16 p.m.