Triple
T29258291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guo clan |
E741764
|
entity |
| Predicate | foundingOfLaterZhou |
P92833
|
FINISHED |
| Object | 951 |
—
|
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: 951 | Statement: [Guo clan, foundingOfLaterZhou, 951]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingOfLaterZhou Context triple: [Guo clan, foundingOfLaterZhou, 951]
-
A.
governingDynastyAtFoundation
Indicates the ruling dynasty that held power at the time an entity (such as a state, city, or institution) was founded.
-
B.
founderDynasty
chosen
Indicates that an entity is the founding member or originator of a particular dynasty.
-
C.
foundingDynastyOf
Indicates that a particular dynasty is the original founding ruling house or lineage of a specified political entity, state, or realm.
-
D.
branchOfDynastyFounded
Indicates that one dynasty is a branch or offshoot of another, earlier-founded dynasty.
-
E.
dynastyFoundedInContextOf
Indicates that a dynasty was established specifically within, or as a consequence of, a particular historical, political, social, or cultural context or circumstance.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 28, 2026, 12:39 p.m.