Triple

T37017390
Position Surface form Disambiguated ID Type / Status
Subject Taihō E916119 entity
Predicate relatedReform P24524 FINISHED
Object Asuka–Kiyomihara Code
The Asuka–Kiyomihara Code was an early Japanese legal code of the late 7th century that laid foundational principles for the ritsuryō state and influenced subsequent reforms such as the Taihō Code.
 E2208353 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: Asuka–Kiyomihara Code | Statement: [Taihō, relatedReform, Asuka–Kiyomihara Code]
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: Asuka–Kiyomihara Code
Triple: [Taihō, relatedReform, Asuka–Kiyomihara Code]
Generated description
The Asuka–Kiyomihara Code was an early Japanese legal code of the late 7th century that laid foundational principles for the ritsuryō state and influenced subsequent reforms such as the Taihō Code.

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_69f76e920dc48190acb6bb7ebc4dffab completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fa0080c6ec8190abb89147a870f334 completed May 5, 2026, 2:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3e5774d8588190aa6e4b8fb72972fd completed June 26, 2026, 10:41 a.m.
NEDg Description generation batch_6a3e591e04f081909832796a584cba51 completed June 26, 2026, 10:49 a.m.
NED2 Entity disambiguation (via description) batch_6a3e5f4a910081908f9ff844c1feb1ae completed June 26, 2026, 11:15 a.m.
Created at: May 3, 2026, 4:14 p.m.