Triple

T25375886
Position Surface form Disambiguated ID Type / Status
Subject Judgment T-622 of 2016 E633054 entity
Predicate instanceOf P0 FINISHED
Object Colombian court decision C4529 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Colombian court decision
Context triple: [Judgment T-622 of 2016, instanceOf, Colombian court decision]
  • A. ley colombiana
    La "ley colombiana" es el conjunto de normas jurídicas vigentes en Colombia, emanadas de la Constitución, el Congreso, el Gobierno y otras autoridades competentes, que regulan la organización del Estado y la conducta de las personas en el territorio nacional.
  • B. Peruvian statute
    A Peruvian statute is a formal written law enacted by Peru’s legislative authority that establishes binding legal rules and obligations within the country’s jurisdiction.
  • C. court decision chosen
    A court decision is a formal, authoritative ruling issued by a judicial body that resolves the legal issues in a case and may establish or apply legal precedent.
  • D. constitutional function of the State of Ecuador
    The constitutional function of the State of Ecuador is the fundamental role or set of duties assigned by the Constitution to a branch or organ of the state—such as legislative, executive, judicial, electoral, or transparency and social control functions—to organize public power and guarantee rights.
  • E. Chilean legal instrument
    A Chilean legal instrument is a formal, legally binding document or act—such as a law, decree, regulation, contract, or judicial decision—issued or recognized under Chilean law to create, modify, interpret, or extinguish rights and obligations.
  • F. None of above.

Provenance (1 batch)

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_69e75a90c0dc819092f928b6ea0ecc72 completed April 21, 2026, 11:08 a.m.
Created at: April 21, 2026, 1:38 p.m.