Triple
T32495510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houyuan |
E830510
|
entity |
| Predicate | eraSequenceInReignOfEmperorWu |
P174198
|
FINISHED |
| Object | last era name |
—
|
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: last era name | Statement: [Houyuan, eraSequenceInReignOfEmperorWu, last era name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraSequenceInReignOfEmperorWu Context triple: [Houyuan, eraSequenceInReignOfEmperorWu, last era name]
-
A.
eraSequenceInEmperorLingReign
Indicates that one era directly follows another within the chronological sequence of Emperor Ling’s reign.
-
B.
eraNumberInReignOfEmperorWu
Indicates the specific numbered era within the reign period of Emperor Wu to which something (such as a date or event) belongs.
-
C.
eraSequenceInEasternWu
Indicates that one era chronologically follows another within the historical sequence of Eastern Wu.
-
D.
eraSequenceWithinDynasty
Indicates that one historical era occurs in a specific ordered position relative to another era within the same dynasty.
-
E.
eraSequenceInReign
chosen
Indicates the ordinal position of a specific era within the chronological sequence of eras that occur during a particular ruler’s reign.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:59 a.m.