Triple
T13513179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wèi Rénmín Fúwù |
E322689
|
entity |
| Predicate | hasOriginalChineseForm |
P6282
|
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: [Wèi Rénmín Fúwù, hasOriginalChineseForm, 为人民服务]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalChineseForm Context triple: [Wèi Rénmín Fúwù, hasOriginalChineseForm, 为人民服务]
-
A.
hasTraditionalCharacter
Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
-
B.
hasChineseVersion
Indicates that an entity has a corresponding version or representation available in Chinese.
-
C.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
D.
ChineseNameTraditional
chosen
Indicates that an entity’s name is given in traditional Chinese characters.
-
E.
cantoneseForm
Indicates that one entity is the Cantonese-language form or representation of another entity.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf87ca288190a147fbdb2f90985f |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:44 p.m.