Triple

T18567267
Position Surface form Disambiguated ID Type / Status
Subject Five Yuan system E453786 entity
Predicate hasCheckAndBalanceRelation P2845 FINISHED
Object Control Yuan oversight of other branches 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: Control Yuan oversight of other branches | Statement: [Five Yuan system, hasCheckAndBalanceRelation, Control Yuan oversight of other branches]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCheckAndBalanceRelation
Context triple: [Five Yuan system, hasCheckAndBalanceRelation, Control Yuan oversight of other branches]
  • A. hasCheckAndBalanceWith
    Indicates that two entities mutually monitor, limit, or counterbalance each other's powers or actions to prevent dominance or abuse.
  • B. hasCheckAndBalanceFunction chosen
    Indicates that one entity performs a checking or limiting role on another entity’s powers, providing oversight and balance within a system.
  • C. hasRelation
    Indicates that there exists some specified relationship or association between two entities.
  • D. hasOnlineBalanceCheck
    Indicates that an entity provides the capability to check a balance via an online interface or service.
  • E. hasSecurityRelationship
    Indicates a relationship in which one entity provides, manages, or is otherwise linked to the security or protection of another entity.
  • 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_69d8d38974308190a9174430ef256b73 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53aff027481909ca7257967967650 completed April 19, 2026, 8:28 p.m.
PD Predicate disambiguation batch_69e478c16e0c8190b03966aa23c395a6 completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 11:43 a.m.