Triple
T28801563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongxi |
E727249
|
entity |
| Predicate | associatedWithPosthumousTitle |
P110011
|
FINISHED |
| Object | Emperor Taizong of Song |
E187544
|
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: Emperor Taizong of Song | Statement: [Yongxi, associatedWithPosthumousTitle, Emperor Taizong of Song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPosthumousTitle Context triple: [Yongxi, associatedWithPosthumousTitle, Emperor Taizong of Song]
-
A.
posthumousTitleOf
chosen
Indicates that one entity is the honorary or formal title granted to another entity after that entity’s death.
-
B.
posthumousTitleIn
Indicates that an entity was granted a specific posthumous title within a particular jurisdiction, period, or context.
-
C.
posthumousTitleYear
Indicates the year in which an entity was formally granted a title or honor after its death.
-
D.
posthumousTitleStatus
Indicates the status or condition of an honorary title that is granted to a person after their death.
-
E.
posthumousAssociation
Indicates an association or connection between entities that is established, recognized, or relevant only after one of the entities has died.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a01d339feac8190a3de56b24db67163 |
completed | May 11, 2026, 1:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34c650930081909de4b6ccdd43fbc3 |
completed | June 19, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_6a01d2bc1f408190a04869f95e6941ee |
completed | May 11, 2026, 12:59 p.m. |
Created at: April 28, 2026, 6:27 a.m.