Triple
T34698629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huichang |
E891103
|
entity |
| Predicate | predecessorEmperorEraContext |
P182769
|
FINISHED |
| Object | Emperor Wenzong 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: Emperor Wenzong of Tang | Statement: [Huichang, predecessorEmperorEraContext, Emperor Wenzong of Tang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorEmperorEraContext Context triple: [Huichang, predecessorEmperorEraContext, Emperor Wenzong of Tang]
-
A.
predecessorRulerEraSystem
Indicates that one ruler’s era or reign immediately preceded another’s within a defined ruling system or succession framework.
-
B.
predecessorEraRuler
Indicates that one ruler directly preceded another as the ruler of a given era or period.
-
C.
precededByMonarchEra
chosen
Indicates that one monarch’s reign or era occurred immediately before another specified monarch’s era in a temporal sequence.
-
D.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
-
E.
precededByEraInSameDynasty
Indicates that one era directly comes before another era within the same dynasty.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 1, 2026, 2:05 a.m.