Triple
T28324407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 司馬懿 |
E717366
|
entity |
| Predicate | dynastyFoundedByFamily |
P114665
|
FINISHED |
| Object | Jin 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: Jin dynasty | Statement: [司馬懿, dynastyFoundedByFamily, Jin dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyFoundedByFamily Context triple: [司馬懿, dynastyFoundedByFamily, Jin dynasty]
-
A.
founderDynasty
Indicates that an entity is the founding member or originator of a particular dynasty.
-
B.
dynastyFoundedByMember
chosen
Indicates that a dynasty was established or initiated by a specific individual who is a member of that dynasty.
-
C.
dynastyFoundedRuledPeriod
Indicates that a particular dynasty was founded and held ruling authority during a specified historical time period.
-
D.
governingDynastyAtFoundation
Indicates the ruling dynasty that held power at the time an entity (such as a state, city, or institution) was founded.
-
E.
dynastyFoundedIn
Indicates that a particular dynasty was established or came into existence in a specified time or place.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:27 a.m.