Triple
T32458250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuanshuo |
E829489
|
entity |
| Predicate | eraNumberInReignOfEmperorWu |
P174481
|
FINISHED |
| Object | seventh era name of Emperor Wu of Han |
—
|
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: seventh era name of Emperor Wu of Han | Statement: [Yuanshuo, eraNumberInReignOfEmperorWu, seventh era name of Emperor Wu of Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNumberInReignOfEmperorWu Context triple: [Yuanshuo, eraNumberInReignOfEmperorWu, seventh era name of Emperor Wu of Han]
-
A.
eraNumberUnderEmperorYang
Indicates that the specified era name or era number was used during the reign of Emperor Yang.
-
B.
eraSequenceInEmperorLingReign
Indicates that one era directly follows another within the chronological sequence of Emperor Ling’s reign.
-
C.
eraNumberInDynasty
Indicates that a specific era is identified by and associated with a particular numbered position within a dynasty.
-
D.
ordinalNumberAsEmperor
Indicates the numerical order in which a person held the title or role of emperor.
-
E.
eraNumberInMing
Indicates that a specific era number is assigned within the historical context of the Ming dynasty.
- 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_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:56 a.m.