Triple
T29969724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhenguan |
E761283
|
entity |
| Predicate | associatedEmperorPersonalName |
P91779
|
FINISHED |
| Object | Li Shimin |
E1898922
|
NE 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: Li Shimin | Statement: [Zhenguan, associatedEmperorPersonalName, Li Shimin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedEmperorPersonalName Context triple: [Zhenguan, associatedEmperorPersonalName, Li Shimin]
-
A.
rulingEmperorPersonalName
Indicates that the specified personal name belongs to the individual who is (or was) serving as the ruling emperor.
-
B.
notableEmperorPersonalName
Indicates that the object is the personal (given) name of an emperor who is historically notable.
-
C.
hasEmperorPersonalName
chosen
Indicates that the specified personal name is the official emperor’s given name borne by the referenced individual.
-
D.
associatedWithEmperor
Indicates a relationship in which an entity has a connection, link, or affiliation with an emperor, such as through service, influence, kinship, or shared authority.
-
E.
eraOfEmperor
Indicates the historical time period during which a particular emperor held power or reigned.
- F. None of above.
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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2870c991f481909ed5fbeb944d86fe |
completed | June 9, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:31 p.m.