Triple
T27766516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cao family |
E701613
|
entity |
| Predicate | predecessorStateInfluence |
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: [Cao family, predecessorStateInfluence, Eastern Han dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorStateInfluence Context triple: [Cao family, predecessorStateInfluence, Eastern Han dynasty]
-
A.
predecessorState
chosen
Indicates that one state directly precedes another in a sequence or process.
-
B.
predecessorStateOf
Indicates that one state occurs immediately before and leads into another state in a sequence or process.
-
C.
predecessorStateConcerned
Indicates that a concern or issue present in a predecessor state is relevant to, or carried over into, the current state.
-
D.
predecessorStateContext
Indicates that one state serves as the immediately preceding state within a given contextual sequence or process.
-
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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 4:31 p.m.