Triple
T13494412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Toba |
E320721
|
entity |
| Predicate | eraNameUsed |
P2938
|
FINISHED |
| Object |
Kyūan
Kyūan was a Japanese era (nengō) of the late Heian period, spanning the reign of Emperor Toba and marked by courtly culture and political intrigue.
|
E1043309
|
NE FINISHED |
How this triple was built (4 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: Kyūan | Statement: [Emperor Toba, eraNameUsed, Kyūan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kyūan Context triple: [Emperor Toba, eraNameUsed, Kyūan]
-
A.
Gyōkyō
Gyōkyō was a Buddhist monk traditionally credited with establishing the important Shinto-Buddhist shrine Iwashimizu Hachimangū in Japan.
-
B.
Taishi
Taishi was the first era name used by Emperor Wu of the Western Han dynasty, marking an important early phase of his long and influential reign in ancient China.
-
C.
Taishi
Taishi is a town in Osaka Prefecture, Japan, known for its historical sites and traditional rural character.
-
D.
Sunpu
Sunpu is the former name of the Japanese castle town that developed into modern Shizuoka City, historically known as a key stronghold of the Tokugawa shogunate.
-
E.
Taihoku
Taihoku was the Japanese colonial-era name for Taipei, which served as the administrative and political center of Taiwan under Japanese rule.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Kyūan Triple: [Emperor Toba, eraNameUsed, Kyūan]
Generated description
Kyūan was a Japanese era (nengō) of the late Heian period, spanning the reign of Emperor Toba and marked by courtly culture and political intrigue.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Kyūan Target entity description: Kyūan was a Japanese era (nengō) of the late Heian period, spanning the reign of Emperor Toba and marked by courtly culture and political intrigue.
-
A.
Gyōkyō
Gyōkyō was a Buddhist monk traditionally credited with establishing the important Shinto-Buddhist shrine Iwashimizu Hachimangū in Japan.
-
B.
Taishi
Taishi is a town in Osaka Prefecture, Japan, known for its historical sites and traditional rural character.
-
C.
Taishi
Taishi was the first era name used by Emperor Wu of the Western Han dynasty, marking an important early phase of his long and influential reign in ancient China.
-
D.
Sunpu
Sunpu is the former name of the Japanese castle town that developed into modern Shizuoka City, historically known as a key stronghold of the Tokugawa shogunate.
-
E.
Taihoku
Taihoku was the Japanese colonial-era name for Taipei, which served as the administrative and political center of Taiwan under Japanese rule.
- F. None of above. chosen
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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4da2c88190a867b53529d39545 |
completed | April 12, 2026, 2:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7463d3a948190aab07a25fd903d4e |
completed | May 3, 2026, 12:57 p.m. |
| NEDg | Description generation | batch_69f7496187988190b42e51f192cd4a80 |
completed | May 3, 2026, 1:10 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f74a0420908190b2b4988cc4d4a20a |
completed | May 3, 2026, 1:13 p.m. |
Created at: April 9, 2026, 9:43 p.m.