Triple
T27959801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun family of Eastern Wu |
E704549
|
entity |
| Predicate | firstEmperorReignStart |
P200338
|
FINISHED |
| Object | 229 |
—
|
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: 229 | Statement: [Sun family of Eastern Wu, firstEmperorReignStart, 229]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEmperorReignStart Context triple: [Sun family of Eastern Wu, firstEmperorReignStart, 229]
-
A.
traditionalFirstEmperorReignStart
Indicates the traditionally recognized starting date of the first emperor’s reign over a given polity or realm.
-
B.
firstRecordedEmperorStatus
Indicates that the subject is recognized as the earliest historically recorded individual to hold the status or title of emperor.
-
C.
reigningEmperorAtStart
Indicates that the subject was the emperor in power at the beginning of a specified period or event.
-
D.
firstEmperorPersonalName
Indicates the personal (given) name of the individual who was the first emperor in a specified imperial line or polity.
-
E.
foundingEmperor
Indicates the person who established or first ruled an empire as its original sovereign.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_69ff841f2f2081908d72d4f878c538a0 |
completed | May 9, 2026, 6:59 p.m. |
Created at: April 27, 2026, 7:30 p.m.