Triple

T5723877
Position Surface form Disambiguated ID Type / Status
Subject Judiciary Department (Maryland) E126212 entity
Predicate typeOfCourtSystem P8214 FINISHED
Object unified state court system 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: unified state court system | Statement: [Judiciary Department (Maryland), typeOfCourtSystem, unified state court system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfCourtSystem
Context triple: [Judiciary Department (Maryland), typeOfCourtSystem, unified state court system]
  • A. typeOfJurisdiction
    Indicates the specific kind or category of legal authority or control that one jurisdiction holds in relation to a given legal or administrative context.
  • B. hasTypeOfCourt chosen
    Indicates that an entity is associated with or classified by a specific type or category of court.
  • C. judicialBody
    Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
  • D. judicialCircuit
    Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
  • E. recognizesCourt
    Indicates that one legal authority formally accepts the legitimacy or jurisdiction of a particular court.
  • 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_69c0082f723881908ce8bb13a0c0f8b7 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c029014588819094a2a0f6f9b66bab completed March 22, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69c021c6488881909bed4a4534d57f70 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:47 p.m.