Triple
T17925632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 解放勋章 |
E448186
|
entity |
| Predicate | 纪念意义 |
P42490
|
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.
commemorativeEvent
Indicates an event held specifically to honor, remember, or mark the significance of a person, group, or past occurrence.
-
B.
memorialization
Indicates the act of preserving the memory or honoring the legacy of someone or something, often through a dedicated object, event, or practice.
-
C.
commemorationDescription
chosen
Indicates a descriptive statement that explains how an event, person, or thing is honored or remembered.
-
D.
commemorativeRelation
Indicates a relationship where one entity serves to honor, remember, or memorialize another entity, event, or person.
-
E.
memorialScope
Indicates the extent or boundaries of what is commemorated or covered by a memorial.
- 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.