Triple
T35713870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Anti-Corruption Bureau |
E1031942
|
entity |
| Predicate | hasOperationalPowers |
P192092
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Central Anti-Corruption Bureau, hasOperationalPowers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperationalPowers Context triple: [Central Anti-Corruption Bureau, hasOperationalPowers, yes]
-
A.
hasRegulatoryPower
Indicates that one entity possesses formal authority to create, enforce, or oversee rules and regulations governing another entity or activity.
-
B.
haveFiscalPowers
Indicates that an entity possesses legal authority or control over financial or budgetary matters.
-
C.
hasStatePowers
Indicates that an entity possesses or exercises the official powers or authorities of a state-level government.
-
D.
hasExecutiveAuthority
Indicates that one entity holds formal decision-making and managerial power over an organization, group, or process.
-
E.
hasExecutivePowerLevel
Indicates that an entity possesses a specified degree or intensity of executive authority or decision-making power within a given context.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:05 p.m.