Triple
T33941229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Takakura |
E870169
|
entity |
| Predicate | mother |
P120
|
FINISHED |
| Object |
Taira no Shigeko
Taira no Shigeko was a noblewoman of the late Heian period and a prominent member of the powerful Taira clan, influential at the imperial court of Japan.
|
E2084185
|
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: Taira no Shigeko | Statement: [Emperor Takakura, mother, Taira no Shigeko]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Taira no Shigeko Triple: [Emperor Takakura, mother, Taira no Shigeko]
Generated description
Taira no Shigeko was a noblewoman of the late Heian period and a prominent member of the powerful Taira clan, influential at the imperial court of Japan.
Provenance (5 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f702369cf881909f9465ce9a48fd2d |
completed | May 3, 2026, 8:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36c1af01fc81908ff6d3a5b188240f |
completed | June 20, 2026, 4:37 p.m. |
| NEDg | Description generation | batch_6a36c265a4588190b415159def7d4690 |
completed | June 20, 2026, 4:40 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a36c4cc187081908cd56a998ab5c90d |
completed | June 20, 2026, 4:50 p.m. |
Created at: May 1, 2026, 1:49 a.m.