Triple

T24743564
Position Surface form Disambiguated ID Type / Status
Subject Lyon County E618630 entity
Predicate hasStateJudicialDistrict P12920 FINISHED
Object Kansas judicial district including Lyon County 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: Kansas judicial district including Lyon County | Statement: [Lyon County, hasStateJudicialDistrict, Kansas judicial district including Lyon County]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStateJudicialDistrict
Context triple: [Lyon County, hasStateJudicialDistrict, Kansas judicial district including Lyon County]
  • A. hasJudicialDistrict chosen
    Indicates that an entity falls within or is associated with a specific judicial district for legal or court-related purposes.
  • B. hasStateCourt
    Indicates that a given jurisdiction or region possesses an official court that operates at the state level.
  • C. hasStateOrDistrict
    Indicates that an entity is associated with, located in, or belongs to a particular state or district.
  • D. judicialCircuit
    Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
  • E. hasJudicialSeat
    Indicates that an entity holds an official position or seat within a judicial body or 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_69e2fab8f95c81908bb9e552cf3280c2 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f44a417a58819081777e18dda149fd completed May 1, 2026, 6:37 a.m.
PD Predicate disambiguation batch_69f442a977b08190b44eac040cb90211 completed May 1, 2026, 6:05 a.m.
Created at: April 18, 2026, 4:19 a.m.