Triple
T27902463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huangchu |
E705672
|
entity |
| Predicate | startDynasty |
P145762
|
FINISHED |
| Object | Cao Wei |
—
|
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: Cao Wei | Statement: [Huangchu, startDynasty, Cao Wei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDynasty Context triple: [Huangchu, startDynasty, Cao Wei]
-
A.
marksBeginningOfDynasty
chosen
Indicates that an event, person, or moment signifies the start or formal establishment of a particular dynasty.
-
B.
creatorDynasty
Indicates the historical dynasty or ruling period during which the creator of an entity lived or was active.
-
C.
founderDynasty
Indicates that an entity is the founding member or originator of a particular dynasty.
-
D.
builtDynastyAround
Indicates establishing and sustaining a long-term, dominant success or legacy centered on a particular person, group, or core element.
-
E.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 27, 2026, 6:43 p.m.