Triple
T28601324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shang dynasty |
E723918
|
entity |
| Predicate | firstRulerTempleName |
P201926
|
FINISHED |
| Object | Taizu |
—
|
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: Taizu | Statement: [Shang dynasty, firstRulerTempleName, Taizu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRulerTempleName Context triple: [Shang dynasty, firstRulerTempleName, Taizu]
-
A.
lastRulerTempleName
Indicates the name of the temple associated with the most recent or final ruler in a given context.
-
B.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
-
C.
firstTempleIn
Indicates that an entity is the earliest or original temple located in a specified place or region.
-
D.
rulingEmperorTempleName
Indicates the temple name assigned to the emperor who is currently ruling.
-
E.
hasEmperorTempleName
Indicates that an emperor is associated with a specific posthumous temple name used in imperial ancestral worship.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a00332eaa0c8190a69ea895576bb0ee |
completed | May 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_6a0032b2ea80819083b89ebb88165933 |
completed | May 10, 2026, 7:24 a.m. |
| PDg | Predicate description generation | batch_6a00332d97b88190bafe39ac6f1904ba |
completed | May 10, 2026, 7:26 a.m. |
Created at: April 28, 2026, 4:24 a.m.