Triple

T7524637
Position Surface form Disambiguated ID Type / Status
Subject Texas Municipal Courts E177859 entity
Predicate jurisdictionTerritory P6190 FINISHED
Object municipal boundaries 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: municipal boundaries | Statement: [Texas Municipal Courts, jurisdictionTerritory, municipal boundaries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: jurisdictionTerritory
Context triple: [Texas Municipal Courts, jurisdictionTerritory, municipal boundaries]
  • A. countryOfJurisdiction
    Indicates the country whose legal authority or jurisdiction governs or applies to a given entity, action, or arrangement.
  • B. countryJurisdiction
    Indicates that one country has legal authority, control, or governing power over a specified territory, entity, or matter.
  • C. definedTerritoryOf
    Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
  • D. isRegionalJurisdictionOf
    Indicates that one entity functions as the governing or administrative authority over a specific geographic region or area.
  • E. legalJurisdiction chosen
    Indicates the legal authority or geographic area whose laws and courts have the power to govern, regulate, or adjudicate matters involving the related entities.
  • 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_69c69f29bf3081909a146aec7755f185 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f7c61b508190b582f54ecbb387e3 completed March 27, 2026, 9:33 p.m.
PD Predicate disambiguation batch_69c6f4d6bb808190bdd04499fd3bceb6 completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:46 p.m.