Triple
T17925623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 解放勋章 |
E448186
|
entity |
| Predicate | 相关制度 |
P60455
|
FINISHED |
| Object | 1955年中国人民解放军军衔制 |
—
|
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: 1955年中国人民解放军军衔制 | Statement: [解放勋章, 相关制度, 1955年中国人民解放军军衔制]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 相关制度 Context triple: [解放勋章, 相关制度, 1955年中国人民解放军军衔制]
-
A.
relatedRegulation
chosen
Indicates that there exists a regulatory rule, law, or directive that is associated with, governs, or is otherwise relevant to the referenced entity or activity.
-
B.
rulesSystem
Indicates that an entity establishes, governs, or defines the rules or structure by which another system or process operates.
-
C.
relatedRule
Indicates that one rule is connected or associated with another rule, typically through some logical, structural, or referential relationship.
-
D.
collaboratingRegime
Indicates that one regime is actively cooperating or working together with another regime toward shared goals or interests.
-
E.
alsoRegulates
Indicates that an entity not only has a primary regulatory effect on a target but additionally regulates that same target through another, supplementary regulatory relationship.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a54e03588190b36a9bb88e4085de |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:20 a.m.