Triple
T32458206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jianyuan |
E829487
|
entity |
| Predicate | eraNumberInHan |
P174196
|
FINISHED |
| Object | one of the early Western Han era names |
—
|
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: one of the early Western Han era names | Statement: [Jianyuan, eraNumberInHan, one of the early Western Han era names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNumberInHan Context triple: [Jianyuan, eraNumberInHan, one of the early Western Han era names]
-
A.
eraNumberInJapan
Indicates the specific numbered position of a historical era within the sequence of Japanese eras.
-
B.
equivalentInJapaneseKanji
Indicates that one entity has the same meaning or value as another entity when written in Japanese Kanji.
-
C.
hanjaName
Indicates that one entity is the Sino-Korean (hanja) written form corresponding to the name of another entity.
-
D.
kangxiRadicalNumber
Indicates the specific Kangxi radical index number associated with a given Chinese character or component.
-
E.
JapaneseNameReading
Indicates that one entity is the reading or pronunciation (e.g., in kana or romaji) of a Japanese name represented by the other entity.
- F. None of above. chosen
Provenance (4 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c31c7e888190840849dda3b90fd2 |
completed | May 3, 2026, 3:38 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:56 a.m.