Triple

T434569
Position Surface form Disambiguated ID Type / Status
Subject United States district courts E9783 entity
Predicate locationScope P13939 FINISHED
Object geographic judicial districts defined by Congress 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: geographic judicial districts defined by Congress | Statement: [United States district courts, locationScope, geographic judicial districts defined by Congress]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locationScope
Context triple: [United States district courts, locationScope, geographic judicial districts defined by Congress]
  • A. teamLocationScope
    Indicates the geographic or organizational area within which a team operates or is considered relevant.
  • B. locationOnUniform
    Indicates that a specific location or marking appears on a uniform.
  • C. organizationalScope
    Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
  • D. locationVariesWith
    Indicates that the location of one entity changes in dependence on, or as a function of, changes in another entity.
  • E. scopeOfUse
    Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
  • 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_69a2e801e1d48190b505d1dd336b52ac completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2ef0a008c8190ae0aa25e4df9c35f completed Feb. 28, 2026, 1:35 p.m.
PD Predicate disambiguation batch_69a2edda55e88190b7c17ba94d7df1ce completed Feb. 28, 2026, 1:30 p.m.
PDg Predicate description generation batch_69a2eeb93584819082f23eff13e17c4f completed Feb. 28, 2026, 1:33 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.