Triple

T1138981
Position Surface form Disambiguated ID Type / Status
Subject People’s Supreme Court E23404 entity
Predicate canConfirm P26465 FINISHED
Object decisions of lower courts 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: decisions of lower courts | Statement: [People’s Supreme Court, canConfirm, decisions of lower courts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canConfirm
Context triple: [People’s Supreme Court, canConfirm, decisions of lower courts]
  • A. canElect
    Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
  • B. canConcurIn
    Indicates that one entity is able or permitted to agree with, coincide with, or participate jointly in the same event, decision, or condition as another entity.
  • C. canAuthorize
    Indicates that one entity has the power or permission to grant approval or official permission for another entity to perform an action or access a resource.
  • D. canPass
    Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
  • E. canReview
    Indicates that one entity has the permission or ability to evaluate, assess, or provide feedback on another entity.
  • F. None of above. chosen

Provenance (4 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_69a493ef399c8190b04b9146d2314f59 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bde18d208190848c189b2b8d585f completed March 1, 2026, 10:29 p.m.
PD Predicate disambiguation batch_69a4bb4b52d48190bec2e7ad1cc8efc0 completed March 1, 2026, 10:18 p.m.
PDg Predicate description generation batch_69a4bddfa598819088690e1ab010ba0b completed March 1, 2026, 10:29 p.m.
Created at: March 1, 2026, 7:44 p.m.