Triple
T35108721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 陳其美 |
E1013224
|
entity |
| Predicate | 紀念 |
P30712
|
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.
開業記念
Indicates a relationship where something is associated with, created for, or occurring in commemoration of an opening (such as the start of a business or facility).
-
C.
commemoratedFor
chosen
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
D.
commemoratesEventWith
Indicates that one entity serves as a memorial or tribute to a specific event, marking or honoring its occurrence.
-
E.
commemoratesField
Indicates that one entity serves to honor, remember, or mark the significance of another entity, event, or achievement.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.