Triple
T32385905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Ying |
E827543
|
entity |
| Predicate | foundedQinDynasty |
P18877
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [House of Ying, foundedQinDynasty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedQinDynasty Context triple: [House of Ying, foundedQinDynasty, true]
-
A.
hasDynastyFounded
chosen
Indicates that an entity is the founder or originator of a particular dynasty.
-
B.
foundingDynastyOf
Indicates that a particular dynasty is the original founding ruling house or lineage of a specified political entity, state, or realm.
-
C.
dynastyFoundedIn
Indicates that a particular dynasty was established or came into existence in a specified time or place.
-
D.
governingDynastyAtFoundation
Indicates the ruling dynasty that held power at the time an entity (such as a state, city, or institution) was founded.
-
E.
dynastyFoundedBecame
Indicates that an entity founded a dynasty and subsequently became its ruler or central figure.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 1, 2026, 12:51 a.m.