Triple
T7947098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 双一流 |
E184523
|
entity |
| Predicate | 政策属性 |
P26219
|
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.
policyFocus
Indicates that an entity (such as a person, organization, or document) is primarily concerned with, directed toward, or centered on a particular policy area or issue.
-
B.
economicPolicyType
Indicates the classification of an economic policy according to its general type or category (e.g., fiscal, monetary, trade).
-
C.
economicPolicyOrientation
Indicates the general stance or approach an entity takes toward economic policy, such as its preferred principles, priorities, or strategies in managing the economy.
-
D.
policyApproach
Indicates the strategy, method, or overall course of action adopted in creating, implementing, or managing a policy.
-
E.
policyCharacteristic
chosen
Indicates that a policy possesses a particular attribute, feature, or quality that characterizes how it is defined or operates.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2abdbc819085ae53826d36af3b |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae9361bc48190886b7681e563d46b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.