Triple
T32458189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jianyuan |
E829487
|
entity |
| Predicate | positionInReign |
P197960
|
FINISHED |
| Object | first 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: first era name of Emperor Wu of Han | Statement: [Jianyuan, positionInReign, first era name of Emperor Wu of Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInReign Context triple: [Jianyuan, positionInReign, first era name of Emperor Wu of Han]
-
A.
positionInDynasty
Indicates the specific role or rank an individual holds within a particular dynasty’s internal hierarchy.
-
B.
activeInReignOf
Indicates that an entity was active or operational during the time period corresponding to a specific ruler’s reign.
-
C.
establishedInReign
Indicates that something (such as an institution, structure, or entity) was founded or created during the period of a specific ruler’s reign.
-
D.
namedDuringReignOf
Indicates that one entity received its name while another entity (typically a ruler or regime) was in power.
-
E.
centuryOfReign
Indicates the century during which a given entity’s reign or rule took place.
- 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_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
| PDg | Predicate description generation | batch_69febce420b081908e1c052751a22b1f |
completed | May 9, 2026, 4:49 a.m. |
Created at: May 1, 2026, 12:56 a.m.