Triple

T4434180
Position Surface form Disambiguated ID Type / Status
Subject District of Columbia federal judicial circuit E95605 entity
Predicate belongsToCircuitNumbering P55986 FINISHED
Object not numbered among the regional circuits 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: not numbered among the regional circuits | Statement: [District of Columbia federal judicial circuit, belongsToCircuitNumbering, not numbered among the regional circuits]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: belongsToCircuitNumbering
Context triple: [District of Columbia federal judicial circuit, belongsToCircuitNumbering, not numbered among the regional circuits]
  • A. belongsToCircuit
    Indicates that something is a component or member of a specific circuit or circuit grouping.
  • B. numberOfCircuitsInSystem
    Indicates the total count of circuits that exist within a given system.
  • C. hasCircuit
    Indicates that an entity is equipped with, contains, or is associated with an electrical or logical circuit.
  • D. servesCircuit
    Indicates that an entity provides legal representation or service in a specified judicial circuit.
  • E. circuitUsed
    Indicates that a particular circuit is utilized or employed in performing an action, process, or function.
  • 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_69b3453ea2b48190a26f154b3b8fece5 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35588e99881908fea7b71a33e2bb6 completed March 13, 2026, 12:08 a.m.
PD Predicate disambiguation batch_69b34f6078cc8190831b89f404198cc5 completed March 12, 2026, 11:42 p.m.
PDg Predicate description generation batch_69b3505a87b4819083fbbd58870e520b completed March 12, 2026, 11:46 p.m.
Created at: March 12, 2026, 11:31 p.m.