Triple

T33744957
Position Surface form Disambiguated ID Type / Status
Subject Court of Appeal of Cambodia E864672 entity
Predicate canQuash P76532 FINISHED
Object lower court judgments 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: lower court judgments | Statement: [Court of Appeal of Cambodia, canQuash, lower court judgments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canQuash
Context triple: [Court of Appeal of Cambodia, canQuash, lower court judgments]
  • A. canSuppress
    Indicates that one entity has the ability or capacity to prevent, inhibit, or reduce the effect, activity, or expression of another entity or process.
  • B. canRejectWith
    Indicates that one entity has the authority or ability to refuse, decline, or dismiss another entity or proposal using a specific method or condition.
  • C. canRepeal chosen
    Indicates that one entity has the authority or power to revoke, annul, or cancel a rule, decision, or action established by another entity.
  • D. canMake
    Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
  • E. canConfirm
    Indicates that one entity has the ability or authority to verify the truth, validity, or occurrence of something related to another entity or event.
  • 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_69f3498b24b8819096a65009e521d0e1 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fb5d436c8190a37a1cc8001319ac completed May 3, 2026, 7:38 a.m.
PD Predicate disambiguation batch_69f6f96dd4c8819093d6a7bd046a9ad5 completed May 3, 2026, 7:29 a.m.
Created at: May 1, 2026, 1:44 a.m.