Triple

T426047
Position Surface form Disambiguated ID Type / Status
Subject Supreme Court of Colombia E9609 entity
Predicate highestCourtFor P6120 FINISHED
Object ordinary jurisdiction in Colombia 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: ordinary jurisdiction in Colombia | Statement: [Supreme Court of Colombia, highestCourtFor, ordinary jurisdiction in Colombia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: highestCourtFor
Context triple: [Supreme Court of Colombia, highestCourtFor, ordinary jurisdiction in Colombia]
  • A. highestCourtOf chosen
    Indicates that one entity is the supreme judicial authority or top-level court within the jurisdiction or legal system of another entity.
  • B. highCourtBench
    Indicates that a particular bench or panel of judges belongs to, or is constituted within, a high court.
  • C. isMajorCourtIn
    Indicates that a court is a primary or high-level judicial body within the specified jurisdiction or region.
  • D. hasLowerCourt
    Indicates that one court functions as a subordinate or inferior court within the judicial hierarchy of another court.
  • E. judicialBody
    Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
  • 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_69a2e801e1d48190b505d1dd336b52ac completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2eed691c4819092b7e57306114bbc completed Feb. 28, 2026, 1:34 p.m.
PD Predicate disambiguation batch_69a2edd6736c81909a6ca549f77b4345 completed Feb. 28, 2026, 1:29 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.