Triple
T36128630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 中国人民解放军预备役人员 |
E1044952
|
entity |
| Predicate | 战略作用 |
P38985
|
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.
strategicAspect
Indicates that something pertains to a strategic dimension, such as long-term planning, positioning, or high-level decision-making within a broader context.
-
B.
strategicCommand
Indicates that one entity issues high-level, overarching directives or plans that guide the actions or decisions of another entity.
-
C.
hasStrategicFunction
chosen
Indicates that an entity serves a planned, goal-oriented role or purpose within a broader strategy or system.
-
D.
militaryStrategy
Indicates a relationship where an entity plans, directs, or is associated with the organized use of armed forces and tactics to achieve military or defense objectives.
-
E.
strategicStance
Indicates the overarching strategic position, approach, or orientation an entity adopts in relation to others or to a particular situation.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.