Triple
T27766596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sima clan |
E701615
|
entity |
| Predicate | unifiedChinaInYear |
P163556
|
FINISHED |
| Object | 280 |
—
|
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: 280 | Statement: [Sima clan, unifiedChinaInYear, 280]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unifiedChinaInYear Context triple: [Sima clan, unifiedChinaInYear, 280]
-
A.
historicalPeriodOfUnification
Indicates the historical time span during which separate entities were unified into a single political or organizational whole.
-
B.
firstEmperorToRuleAllChina
Indicates that the subject was the earliest emperor to unify and govern all of China under a single centralized rule.
-
C.
reunifiedAsCapitalInYear
Indicates that an entity regained its status as a capital city in a specified year after a period of not holding that status.
-
D.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
E.
mainlandNameAfterUnion
Indicates that the predicate links an entity to the name used for its mainland territory after a political or administrative union has taken place.
- F. None of above. chosen
Provenance (4 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 4:31 p.m.