Triple
T30831139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baoying |
E785220
|
entity |
| Predicate | followedByMonarchEra |
P182769
|
FINISHED |
| Object | Jianzhong (Emperor Daizong of Tang) |
—
|
NE NERFINISHED |
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: Jianzhong (Emperor Daizong of Tang) | Statement: [Baoying, followedByMonarchEra, Jianzhong (Emperor Daizong of Tang)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByMonarchEra Context triple: [Baoying, followedByMonarchEra, Jianzhong (Emperor Daizong of Tang)]
-
A.
precededByMonarchEra
chosen
Indicates that one monarch’s reign or era occurred immediately before another specified monarch’s era in a temporal sequence.
-
B.
cameUnderSameMonarchAs
Indicates that two entities were, at some point in time, both subject to rule by the same monarch.
-
C.
ruledLaterBy
Indicates that one entity came under the rule, governance, or authority of another entity at a later point in time.
-
D.
governingMonarchs
Indicates that the subject is the monarch who holds ruling authority over the object (such as a country, territory, or people).
-
E.
successorEraRuler
Indicates that one ruler directly succeeds another as the ruler of a given era or period.
- 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 29, 2026, 8:44 p.m.