Triple
T28096124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenfeng |
E710095
|
entity |
| Predicate | usedInSuccessorStateOf |
P86176
|
FINISHED |
| Object | 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: Han dynasty | Statement: [Shenfeng, usedInSuccessorStateOf, Han dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSuccessorStateOf Context triple: [Shenfeng, usedInSuccessorStateOf, Han dynasty]
-
A.
successorStateUse
Indicates that one state or condition directly follows and is used as the next state resulting from a prior state or action.
-
B.
successorUsedIn
chosen
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
-
C.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
-
D.
associatedWithSuccessorState
Indicates a relationship where something is linked or connected to the state that immediately follows it in a sequence or progression.
-
E.
predecessorStateOf
Indicates that one state occurs immediately before and leads into another state 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 9:01 p.m.