Triple
T30716469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 中国人民银行货币金银局 |
E782034
|
entity |
| Predicate | 监管对象 |
P170064
|
FINISHED |
| Object | 贵金属业务 |
—
|
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: 贵金属业务 | Statement: [中国人民银行货币金银局, 监管对象, 贵金属业务]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 监管对象 Context triple: [中国人民银行货币金银局, 监管对象, 贵金属业务]
-
A.
管理区分
Indicates a classification used to distinguish how something is managed, controlled, or administered.
-
B.
管制方式
Indicates the method or mode by which control, regulation, or management is exercised over a target or process.
-
C.
评选对象
Indicates the entities that are chosen or designated as candidates or subjects for evaluation, selection, or judging in an assessment or award process.
-
D.
相关政策
Indicates that there exists a relevant or associated policy that applies to, governs, or influences the specified entity or situation.
-
E.
regulatorsInvolved
Indicates that one or more regulatory authorities are involved in overseeing, reviewing, or influencing the referenced entity or activity.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c5343b8819082ded39e2e8ee1c8 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:35 p.m.