Triple
T38135800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xinhai |
E952347
|
entity |
| Predicate | HeavenlyStemChinese |
P190134
|
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, HeavenlyStemChinese, 辛]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HeavenlyStemChinese Context triple: [Xinhai, HeavenlyStemChinese, 辛]
-
A.
HeavenlyStem
chosen
Indicates a relationship where an entity is associated with one of the traditional Chinese Heavenly Stems used for cyclical designation in calendars and related systems.
-
B.
heavenlyStemsCycleLength
Indicates the length of the repeating cycle of the Heavenly Stems sequence in a calendrical or ordinal system.
-
C.
isZodiacStar
Indicates that one entity is a zodiac star (or sign) associated with, or characterizing, the other entity.
-
D.
zodiacSystem
Indicates a relationship where an entity is associated with, defined by, or classified under a particular zodiac system or framework.
-
E.
ChineseNameMeaning
Indicates that the predicate specifies the semantic meaning or interpretation of a given Chinese name.
- 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_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:21 p.m.