Triple

T10238881
Position Surface form Disambiguated ID Type / Status
Subject Emperor Nintoku E243537 entity
Predicate nativeName P15 FINISHED
Object 仁徳天皇
仁徳天皇は、日本の古代における第16代天皇とされ、大阪府堺市の巨大前方後円墳(仁徳天皇陵古墳)で特に知られる伝説的君主である。
E853363 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: 仁徳天皇 | Statement: [Emperor Nintoku, nativeName, 仁徳天皇]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 仁徳天皇
Context triple: [Emperor Nintoku, nativeName, 仁徳天皇]
  • A. 孝明天皇
    孝明天皇は、幕末の動乱期に在位し、尊王攘夷運動や公武合体政策の中心となった日本の第121代天皇である。
  • B. Emperor Sanjō
    Emperor Sanjō was the 67th emperor of Japan, a Heian-period monarch whose reign was marked by the political dominance of the Fujiwara regents.
  • C. Emperor Kinmei
    Emperor Kinmei was a 6th-century Japanese monarch traditionally regarded as one of the earliest reliably documented emperors of Japan, marking the beginning of historically attested imperial rule.
  • D. Emperor Go-Toba
    Emperor Go-Toba was a late 12th- to early 13th-century Japanese emperor known for his cultural patronage, especially of poetry, and for leading the failed Jōkyū War against the Kamakura shogunate.
  • E. Emperor Go-Sanjō
    Emperor Go-Sanjō was the 71st emperor of Japan, known for his efforts to strengthen imperial authority and reform the administration during the late Heian period.
  • 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: 仁徳天皇
Triple: [Emperor Nintoku, nativeName, 仁徳天皇]
Generated description
仁徳天皇は、日本の古代における第16代天皇とされ、大阪府堺市の巨大前方後円墳(仁徳天皇陵古墳)で特に知られる伝説的君主である。
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: 仁徳天皇
Target entity description: 仁徳天皇は、日本の古代における第16代天皇とされ、大阪府堺市の巨大前方後円墳(仁徳天皇陵古墳)で特に知られる伝説的君主である。
  • A. 孝明天皇
    孝明天皇は、幕末の動乱期に在位し、尊王攘夷運動や公武合体政策の中心となった日本の第121代天皇である。
  • B. Emperor Sanjō
    Emperor Sanjō was the 67th emperor of Japan, a Heian-period monarch whose reign was marked by the political dominance of the Fujiwara regents.
  • C. Emperor Kinmei
    Emperor Kinmei was a 6th-century Japanese monarch traditionally regarded as one of the earliest reliably documented emperors of Japan, marking the beginning of historically attested imperial rule.
  • D. Emperor Go-Toba
    Emperor Go-Toba was a late 12th- to early 13th-century Japanese emperor known for his cultural patronage, especially of poetry, and for leading the failed Jōkyū War against the Kamakura shogunate.
  • E. Emperor Go-Sanjō
    Emperor Go-Sanjō was the 71st emperor of Japan, known for his efforts to strengthen imperial authority and reform the administration during the late Heian period.
  • 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_69d381b0f97c819085c9b45799a5fb7c completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d21ca3008190bfbde4074b37592d completed April 7, 2026, 9:45 a.m.
NED1 Entity disambiguation (via context triple) batch_69d6f76ca8848190a49d7dc76cf9dd35 completed April 9, 2026, 12:48 a.m.
NEDg Description generation batch_69d6fa2f7a848190a9de5de4d0f3f110 completed April 9, 2026, 1 a.m.
NED2 Entity disambiguation (via description) batch_69d6fcbab3ec8190ade1c0223c22ad58 completed April 9, 2026, 1:11 a.m.
Created at: April 6, 2026, 11:23 a.m.