Triple
T7947124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 985工程 |
E184524
|
entity |
| Predicate | 提出背景 |
P13994
|
FINISHED |
| Object | 面向21世纪教育振兴行动计划 |
—
|
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: 面向21世纪教育振兴行动计划 | Statement: [985工程, 提出背景, 面向21世纪教育振兴行动计划]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 提出背景 Context triple: [985工程, 提出背景, 面向21世纪教育振兴行动计划]
-
A.
proposedInContextOf
chosen
Indicates that something (such as an idea, action, or change) was proposed specifically within, and in relation to, a particular situation, setting, or surrounding circumstances.
-
B.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
C.
context
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
D.
establishedInResponseTo
Indicates that something was created, initiated, or set up as a direct reaction to a specific event, condition, or stimulus.
-
E.
originalReason
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
- 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.