Triple

T36993970
Position Surface form Disambiguated ID Type / Status
Subject 続日本紀 E915179 entity
Predicate usedAsSourceFor P7051 FINISHED
Object 日本紀略
日本紀略 is a medieval Japanese historical chronicle that compiles and summarizes earlier official histories and records of the imperial court.
E2211116 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: 日本紀略 | Statement: [続日本紀, usedAsSourceFor, 日本紀略]
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: [続日本紀, usedAsSourceFor, 日本紀略]
Generated description
日本紀略 is a medieval Japanese historical chronicle that compiles and summarizes earlier official histories and records of the imperial court.

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_69f76e8f1a8c81909db172ed31304971 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f9ffe0215c81909a5cc04c45624916 completed May 5, 2026, 2:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3e8c2de9c881908d77f51685517ced completed June 26, 2026, 2:26 p.m.
NEDg Description generation batch_6a3e9f60aadc8190a53ee405e98fba5d completed June 26, 2026, 3:48 p.m.
NED2 Entity disambiguation (via description) batch_6a3eacd8e22081909bce3cba6710e2e8 completed June 26, 2026, 4:46 p.m.
Created at: May 3, 2026, 4:14 p.m.