Triple
T32385910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Ying |
E827543
|
entity |
| Predicate | producedFirstEmperorOfUnifiedChina |
P112277
|
FINISHED |
| Object | Qin Shi Huang |
—
|
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: Qin Shi Huang | Statement: [House of Ying, producedFirstEmperorOfUnifiedChina, Qin Shi Huang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedFirstEmperorOfUnifiedChina Context triple: [House of Ying, producedFirstEmperorOfUnifiedChina, Qin Shi Huang]
-
A.
firstEmperorToRuleAllChina
chosen
Indicates that the subject was the earliest emperor to unify and govern all of China under a single centralized rule.
-
B.
traditionalFirstEmperor
Indicates that the subject is regarded, in traditional or legendary accounts, as the first emperor of the object polity or realm.
-
C.
foundingEmperor
Indicates the person who established or first ruled an empire as its original sovereign.
-
D.
traditionalFirstEmperorReignStart
Indicates the traditionally recognized starting date of the first emperor’s reign over a given polity or realm.
-
E.
firstEmperorPersonalName
Indicates the personal (given) name of the individual who was the first emperor in a specified imperial line or polity.
- 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_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 1, 2026, 12:51 a.m.