Triple
T38662429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhōnghuá Mínguó Guóqìngrì |
E940367
|
entity |
| Predicate | ChineseCharactersSimplified |
P6283
|
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: [Zhōnghuá Mínguó Guóqìngrì, ChineseCharactersSimplified, 中华民国国庆日]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChineseCharactersSimplified Context triple: [Zhōnghuá Mínguó Guóqìngrì, ChineseCharactersSimplified, 中华民国国庆日]
-
A.
ChineseNameSimplified
chosen
Indicates that an entity’s name is given in simplified Chinese characters.
-
B.
characterUnicodeSimplified
Indicates that one entity is the simplified-Unicode character form corresponding to another character entity.
-
C.
usedChineseCharacters
Indicates that one entity employed or wrote using Chinese characters in relation to another entity or context.
-
D.
ChinesePinyin
Indicates that one entity is the Chinese pinyin (romanized phonetic transcription) representation of another entity.
-
E.
ChineseNameTraditional
Indicates that an entity’s name is given in traditional Chinese characters.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:33 p.m.