Triple

T7540548
Position Surface form Disambiguated ID Type / Status
Subject Fourth Appellate District E178262 entity
Predicate courtStructure P242 FINISHED
Object multi-division appellate court 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: multi-division appellate court | Statement: [Fourth Appellate District, courtStructure, multi-division appellate court]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: courtStructure
Context triple: [Fourth Appellate District, courtStructure, multi-division appellate court]
  • A. judicialBody chosen
    Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
  • B. courtStyle
    Indicates the manner or stylistic approach in which a court conducts its proceedings or presents its decisions.
  • C. courtRank
    Indicates the formal hierarchical rank or status an individual holds within a court or courtly system.
  • D. judicialCircuit
    Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
  • E. trialCourt
    Indicates that a legal matter, decision, or proceeding is associated with, handled by, or occurring in a court of first instance (the trial-level 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_69c69f2be3888190a6667a27f8f195e9 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f873b17081908bb70aea0010d072 completed March 27, 2026, 9:36 p.m.
PD Predicate disambiguation batch_69c6f4d8eedc81908c1ae421e0e63798 completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:48 p.m.