Triple
T29703387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiping |
E751553
|
entity |
| Predicate | ChineseEraNameType |
P30359
|
FINISHED |
| Object | nianhao |
—
|
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: nianhao | Statement: [Xiping, ChineseEraNameType, nianhao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChineseEraNameType Context triple: [Xiping, ChineseEraNameType, nianhao]
-
A.
usedChineseEraNames
Indicates that one entity employed or referenced Chinese era names in relation to another entity or context.
-
B.
timeInChineseEraSystem
chosen
Indicates that a temporal reference is expressed using a specific Chinese era-based calendrical system (such as reign titles or traditional era names).
-
C.
preModernJapaneseEraSequence
Indicates that one pre-modern Japanese era chronologically precedes another in the historical sequence of eras.
-
D.
dynasticEraName
Indicates the named historical period or era associated with a particular dynasty’s rule.
-
E.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672b5fcf88190b3f6b1d57529ea8a |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:25 p.m.