Triple

T31022480
Position Surface form Disambiguated ID Type / Status
Subject XHKG E790485 entity
Predicate hasRegulatoryUse P202856 FINISHED
Object trade and transaction reporting to regulators 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: trade and transaction reporting to regulators | Statement: [XHKG, hasRegulatoryUse, trade and transaction reporting to regulators]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegulatoryUse
Context triple: [XHKG, hasRegulatoryUse, trade and transaction reporting to regulators]
  • A. regulatesUse
    Indicates that one entity controls, governs, or sets rules for how another entity may be used.
  • B. hasRegulatoryApproval
    Indicates that an entity has received formal authorization or clearance from a relevant regulatory authority to operate, be sold, or be used in a specified context.
  • C. hasRegulatedBy
    Indicates that one entity is subject to control, governance, or rules imposed by another entity.
  • D. allowsRegulationOf
    Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
  • E. hasRegulations
    Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of 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_69f224c811508190a7de096a5b1f5798 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_6a00c59b03dc8190870f0dd24603a1ef completed May 10, 2026, 5:51 p.m.
PD Predicate disambiguation batch_6a00c5178bc88190b2a0e03f38314035 completed May 10, 2026, 5:49 p.m.
PDg Predicate description generation batch_6a00c59a1af88190848c5b1775af9caa completed May 10, 2026, 5:51 p.m.
Created at: April 29, 2026, 8:58 p.m.