Triple

T3325502
Position Surface form Disambiguated ID Type / Status
Subject Payments System Board E69904 entity
Predicate canUsePower P544 FINISHED
Object to set standards for payment systems 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: to set standards for payment systems | Statement: [Payments System Board, canUsePower, to set standards for payment systems]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canUsePower
Context triple: [Payments System Board, canUsePower, to set standards for payment systems]
  • A. hasPower chosen
    Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
  • B. canUse
    Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
  • C. reservesPowerTo
    Indicates that one party retains or explicitly keeps for itself the authority or right to exercise a particular power or function, rather than granting it to others.
  • D. canElect
    Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
  • E. airPowerUsedBy
    Indicates that a particular actor employs or deploys air power (such as aircraft or aerial operations) as part of its activities or capabilities.
  • 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_69ad85a1829881908942c14075644d0d completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb16ca13c8190aea8caed8ccd9b88 completed March 8, 2026, 5:27 p.m.
PD Predicate disambiguation batch_69ada42a19348190a3862ce02451f4aa completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:11 p.m.