Triple

T28791013
Position Surface form Disambiguated ID Type / Status
Subject Yamashina-no-miya E726952 entity
Predicate hasTitleStyle P1609 FINISHED
Object Princess Yamashina
Princess Yamashina is a Japanese imperial princess belonging to the Yamashina-no-miya, one of the former collateral branches of the Imperial House of Japan.
E1843147 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: Princess Yamashina | Statement: [Yamashina-no-miya, hasTitleStyle, Princess Yamashina]
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: Princess Yamashina
Triple: [Yamashina-no-miya, hasTitleStyle, Princess Yamashina]
Generated description
Princess Yamashina is a Japanese imperial princess belonging to the Yamashina-no-miya, one of the former collateral branches of the Imperial House 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_69f0319aabec81908368720196f69a35 completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f6587a3c2881909133d37c1674df4a completed May 2, 2026, 8:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24ec27c2508190ba399278ad044d41 completed June 7, 2026, 3:57 a.m.
NEDg Description generation batch_6a24f066b990819095925ff855a3370e completed June 7, 2026, 4:15 a.m.
NED2 Entity disambiguation (via description) batch_6a24f4d232f08190808f832d0536033c completed June 7, 2026, 4:34 a.m.
Created at: April 28, 2026, 6:23 a.m.