Triple

T38675502
Position Surface form Disambiguated ID Type / Status
Subject Ren’ai Jiao E943727 entity
Predicate governanceClaim P93188 FINISHED
Object de facto control contested 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: de facto control contested | Statement: [Ren’ai Jiao, governanceClaim, de facto control contested]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governanceClaim
Context triple: [Ren’ai Jiao, governanceClaim, de facto control contested]
  • A. governanceToken
    Indicates that one entity functions as a governance token for another, conferring rights to participate in decision-making or control over that entity’s governance.
  • B. governanceRecord
    Indicates that there exists a documented governance-related action, decision, or oversight event associated with the entities involved.
  • C. governanceSeat
    Indicates that an entity serves as the official location or seat where another entity’s governance or administrative authority is based or exercised.
  • D. claimableBy
    Indicates that something is eligible to be claimed, received, or taken by a specified entity.
  • E. claimsToGovern chosen
    Indicates that one entity asserts or maintains that it has governing authority or control over another entity or domain.
  • 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_69f76eec28708190b9c82a505fc278e0 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a037c9141dc819098d7fcc36e69882c completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a2026248190b894436a578d79ac completed May 12, 2026, 7:06 p.m.
Created at: May 3, 2026, 4:33 p.m.