Triple

T17244371
Position Surface form Disambiguated ID Type / Status
Subject Guale people E418582 entity
Predicate wereDisplacedBy P121396 FINISHED
Object English colonial 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: English colonial expansion | Statement: [Guale people, wereDisplacedBy, English colonial expansion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wereDisplacedBy
Context triple: [Guale people, wereDisplacedBy, English colonial expansion]
  • A. displacedBy
    Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
  • B. dispossessedBy
    Indicates that one entity has been deprived of possession, control, or ownership of something as a result of the actions of another entity.
  • C. influencedRelocationOf
    Indicates that one entity played a causal or motivating role in another entity’s decision or action to move from one location to another.
  • D. evacuatedBy
    Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
  • E. colonialDisplacement chosen
    Indicates the forced or coerced removal, relocation, or dispossession of people or communities as a result of colonial expansion, rule, or policies.
  • 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_69d886d8e96081909870bff6c3d0bf09 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42e22fb2c8190aea5d3872095bf46 completed April 19, 2026, 1:21 a.m.
PD Predicate disambiguation batch_69e3832553ac819091aa917c84f755b6 completed April 18, 2026, 1:12 p.m.
Created at: April 10, 2026, 5:39 a.m.