Triple
T17925631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 解放勋章 |
E448186
|
entity |
| Predicate | 历史状态 |
P4711
|
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.
historicalState
chosen
Indicates that an entity existed in a particular state or condition during a specified time in the past.
-
B.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
C.
historicalRecordStatus
Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
-
D.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
-
E.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
- 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.