Triple
T29258171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 後周 |
E741761
|
entity |
| Predicate | firstEmperorTempleName |
P201926
|
FINISHED |
| Object | 太祖 |
—
|
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: 太祖 | Statement: [後周, firstEmperorTempleName, 太祖]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEmperorTempleName Context triple: [後周, firstEmperorTempleName, 太祖]
-
A.
firstEmperorPersonalName
Indicates the personal (given) name of the individual who was the first emperor in a specified imperial line or polity.
-
B.
firstRulerTempleName
chosen
Indicates the name of the temple associated with the first ruler of an entity or domain.
-
C.
rulingEmperorTempleName
Indicates the temple name assigned to the emperor who is currently ruling.
-
D.
hasEmperorTempleName
Indicates that an emperor is associated with a specific posthumous temple name used in imperial ancestral worship.
-
E.
eraNameForEmperor
Indicates that a particular era name is officially associated with or designated for a specific emperor.
- 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_6a00b2b425a8819091ff65695e98c3af |
completed | May 10, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_6a00b06efa248190b2d16b4889185119 |
completed | May 10, 2026, 4:21 p.m. |
Created at: April 28, 2026, 12:39 p.m.