Triple

T37977749
Position Surface form Disambiguated ID Type / Status
Subject Euchee E947468 entity
Predicate removedUnderPolicy P166550 FINISHED
Object Indian Removal policy of the United States NE NERFINISHED

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: Indian Removal policy of the United States | Statement: [Euchee, removedUnderPolicy, Indian Removal policy of the United States]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: removedUnderPolicy
Context triple: [Euchee, removedUnderPolicy, Indian Removal policy of the United States]
  • A. removedUnder chosen
    Indicates that one entity was taken away, eliminated, or withdrawn while being subject to the authority, control, or conditions imposed by another entity.
  • B. removedAs
    Indicates that one entity has been taken out of a position, role, or context in relation to another entity.
  • C. removedAfter
    Indicates that one entity is removed or deleted at a point in time that occurs after the removal or deletion of another entity.
  • D. removedOn
    Indicates that an entity was taken away, deleted, or detached at a specific point in time.
  • E. removedFrom
    Indicates that one entity has been taken away, extracted, or detached from another entity or context.
  • 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_69f76ef7db908190bba6086673a32300 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbc7b78f9481909f4f8fc2e3fdcde1 completed May 6, 2026, 10:59 p.m.
PD Predicate disambiguation batch_69fbbd18c9908190928d274f8731dfa8 completed May 6, 2026, 10:13 p.m.
Created at: May 3, 2026, 4:20 p.m.