Triple
T7877843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cao Wei |
E182901
|
entity |
| Predicate | establishedByEvent |
P36079
|
FINISHED |
| Object | abdication of Emperor Xian of Han |
—
|
LITERAL FINISHED |
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: abdication of Emperor Xian of Han | Statement: [Cao Wei, establishedByEvent, abdication of Emperor Xian of Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedByEvent Context triple: [Cao Wei, establishedByEvent, abdication of Emperor Xian of Han]
-
A.
establishedOnEvent
chosen
Indicates that something (such as a relationship, status, or entity) was created, initiated, or formally established as a direct result of a specific event.
-
B.
establishedForEvent
Indicates that something (such as an organization, structure, or arrangement) was created or set up specifically for a particular event.
-
C.
adoptedAtEvent
Indicates that an entity formally became an adopter or was officially adopted during a specific event.
-
D.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
-
E.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39bd64e481909f699e7dd2818b8f |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:57 p.m.