Triple
T38662428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhōnghuá Mínguó Guóqìngrì |
E940367
|
entity |
| Predicate | ChineseCharactersTraditional |
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: [Zhōnghuá Mínguó Guóqìngrì, ChineseCharactersTraditional, 中華民國國慶日]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChineseCharactersTraditional Context triple: [Zhōnghuá Mínguó Guóqìngrì, ChineseCharactersTraditional, 中華民國國慶日]
-
A.
ChineseNameTraditional
chosen
Indicates that an entity’s name is given in traditional Chinese characters.
-
B.
hasTraditionalCharacter
Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
-
C.
usedChineseCharacters
Indicates that one entity employed or wrote using Chinese characters in relation to another entity or context.
-
D.
characterUnicodeSimplified
Indicates that one entity is the simplified-Unicode character form corresponding to another character entity.
-
E.
ChineseVariant
Indicates that one linguistic form is a variant of another within the Chinese language (e.g., differing by script, region, or orthographic convention).
- 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_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.