Triple

T26981055
Position Surface form Disambiguated ID Type / Status
Subject Indian Country E679600 entity
Predicate hasLegalSignificanceFor P62483 FINISHED
Object criminal jurisdiction 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: criminal jurisdiction | Statement: [Indian Country, hasLegalSignificanceFor, criminal jurisdiction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLegalSignificanceFor
Context triple: [Indian Country, hasLegalSignificanceFor, criminal jurisdiction]
  • A. legalSignificance
    Indicates that something has recognized importance, effect, or consequence within a legal context or system.
  • B. hasLegalRelevanceIn chosen
    Indicates that something is legally significant, applicable, or has consequences within a specified legal context, case, or jurisdiction.
  • C. hasOngoingLegalSignificance
    Indicates that a legal matter, status, or decision continues to have current relevance, effect, or consequences under the law.
  • D. hasLegalEffect
    Indicates that an action, document, or condition produces recognized legal consequences or enforceable rights and obligations.
  • E. hasLegalForceAs
    Indicates that one thing possesses the binding legal effect or validity in the capacity or role of another specified thing.
  • 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_69eeeb507a7081909d516e1fa08b7d29 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f6b49436b0819094e21603054d05d4 completed May 3, 2026, 2:36 a.m.
PD Predicate disambiguation batch_69f6b3a5fd8481909433e923c5e24e55 completed May 3, 2026, 2:32 a.m.
Created at: April 27, 2026, 6:45 a.m.