Triple
T28047110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuande |
E708713
|
entity |
| Predicate | bearerPredecessorState |
P10077
|
FINISHED |
| Object | Eastern Han dynasty |
—
|
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: Eastern Han dynasty | Statement: [Xuande, bearerPredecessorState, Eastern Han dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerPredecessorState Context triple: [Xuande, bearerPredecessorState, Eastern Han dynasty]
-
A.
bearerPredecessor
Indicates that one entity previously held a role, title, or position that is now held by another entity, establishing a predecessor-successor relationship between them.
-
B.
predecessorState
chosen
Indicates that one state directly precedes another in a sequence or process.
-
C.
predecessorStateOf
Indicates that one state occurs immediately before and leads into another state in a sequence or process.
-
D.
bearerSuccessor
Indicates that one bearer entity succeeds or follows another in holding a particular role, title, or responsibility.
-
E.
predecessorStatus
Indicates that one entity’s status is determined by, or directly follows from, the status of a preceding entity in a sequence or process.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 8:30 p.m.