Triple

T7113070
Position Surface form Disambiguated ID Type / Status
Subject United States in litigation involving Indian tribes E165749 entity
Predicate mayWaive P11750 FINISHED
Object sovereign immunity 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: sovereign immunity | Statement: [United States in litigation involving Indian tribes, mayWaive, sovereign immunity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayWaive
Context triple: [United States in litigation involving Indian tribes, mayWaive, sovereign immunity]
  • A. mayReject
    Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
  • B. mayGrant
    Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
  • C. standardOfWaiver chosen
    Indicates the legal criteria or conditions under which a right, claim, or requirement can be voluntarily relinquished or waived.
  • D. mayRemove
    Indicates that one entity is permitted or authorized to remove another entity or its association.
  • E. mayNot
    Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
  • 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_69c6888120f081908f8f01b201dc4a4c completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e5ef813c8190bec0ab0cbae430e5 completed March 27, 2026, 8:17 p.m.
PD Predicate disambiguation batch_69c6e1c4f9788190830288d00cc37026 completed March 27, 2026, 8 p.m.
Created at: March 27, 2026, 2:43 p.m.