Triple
T28468849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lingzong |
E720373
|
entity |
| Predicate | posthumouslyBestowedBy |
P43819
|
FINISHED |
| Object | Eastern Han imperial court |
—
|
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: Eastern Han imperial court | Statement: [Lingzong, posthumouslyBestowedBy, Eastern Han imperial court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumouslyBestowedBy Context triple: [Lingzong, posthumouslyBestowedBy, Eastern Han imperial court]
-
A.
isPosthumousAwardRecipientOf
chosen
Indicates that an entity received an award that was granted after their death.
-
B.
canBeAwardedPosthumously
Indicates that something (such as an honor, title, or award) is eligible to be granted to a person after their death.
-
C.
posthumousAssociation
Indicates an association or connection between entities that is established, recognized, or relevant only after one of the entities has died.
-
D.
posthumousTitleOf
Indicates that one entity is the honorary or formal title granted to another entity after that entity’s death.
-
E.
namedAwardAfter
Indicates that an award has been given a name in honor of or derived from a particular person, group, or entity.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 2:47 a.m.