Triple
T32586514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Sunmyeonghyo |
E832935
|
entity |
| Predicate | honorificPosthumousName |
P110011
|
FINISHED |
| Object | Sunmyeonghyo |
—
|
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: Sunmyeonghyo | Statement: [Empress Sunmyeonghyo, honorificPosthumousName, Sunmyeonghyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificPosthumousName Context triple: [Empress Sunmyeonghyo, honorificPosthumousName, Sunmyeonghyo]
-
A.
posthumousNameType
Indicates the specific category or style of a posthumous name assigned to a person after their death.
-
B.
hasEmperorPosthumousName
Indicates that an individual has been granted or is known by a specific posthumous name used for emperors.
-
C.
isPosthumousNameOf
Indicates that one name is a posthumous title or designation that was given to and refers to a person after their death.
-
D.
posthumousNameLanguage
Indicates the language in which a person's posthumous name is expressed.
-
E.
posthumousTitleOf
chosen
Indicates that one entity is the honorary or formal title granted to another entity after that entity’s death.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:04 a.m.