Triple
T27688746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qianyuan |
E698101
|
entity |
| Predicate | chronologicalPositionInReign |
P6045
|
FINISHED |
| Object | middle reign era of Emperor Jing 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: middle reign era of Emperor Jing of Han | Statement: [Qianyuan, chronologicalPositionInReign, middle reign era of Emperor Jing of Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPositionInReign Context triple: [Qianyuan, chronologicalPositionInReign, middle reign era of Emperor Jing of Han]
-
A.
yearOfReign
Indicates the specific year or span of years during which a ruler or authority held official power or reigned.
-
B.
centuryOfReign
Indicates the century during which a given entity’s reign or rule took place.
-
C.
chronologyWithinReignOf
chosen
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
-
D.
placedOnThrone
Indicates that an entity is formally elevated to a position of rulership or authority, typically by being seated on a throne.
-
E.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 2:51 p.m.