Triple
T38135797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xinhai |
E952347
|
entity |
| Predicate | Chinese characters |
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: [Xinhai, Chinese characters, 辛亥]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Chinese characters Context triple: [Xinhai, Chinese characters, 辛亥]
-
A.
usedChineseCharacters
Indicates that one entity employed or wrote using Chinese characters in relation to another entity or context.
-
B.
ChineseVariant
Indicates that one linguistic form is a variant of another within the Chinese language (e.g., differing by script, region, or orthographic convention).
-
C.
ChineseNameTraditional
chosen
Indicates that an entity’s name is given in traditional Chinese characters.
-
D.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
E.
hasTraditionalCharacter
Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.