Triple
T36128629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 中国人民解放军预备役人员 |
E1044952
|
entity |
| Predicate | 政策保障 |
P79029
|
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.
相关政策
chosen
Indicates that there exists a relevant or associated policy that applies to, governs, or influences the specified entity or situation.
-
B.
安全保障政策
Indicates a relationship where an authority or organization establishes and implements policies and measures to ensure the security and protection of a state or community from threats.
-
C.
制度贡献
Indicates a contribution made through establishing, improving, or supporting systems, institutions, or institutional arrangements.
-
D.
保护属性
Indicates a protective relationship where one entity safeguards, preserves, or defends the attributes or properties of another entity.
-
E.
保护状态
Indicates the protective status or conservation level currently applied to an entity (e.g., how strictly it is protected or conserved).
- 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.