Triple

T17653382
Position Surface form Disambiguated ID Type / Status
Subject Konoe family E429552 entity
Predicate producedMember P103647 FINISHED
Object Konoe Motosaki
Konoe Motosaki was a member of the prestigious Konoe family, one of the leading kuge (court noble) lineages of Japan’s aristocracy.
E1903993 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: Konoe Motosaki | Statement: [Konoe family, producedMember, Konoe Motosaki]
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: Konoe Motosaki
Triple: [Konoe family, producedMember, Konoe Motosaki]
Generated description
Konoe Motosaki was a member of the prestigious Konoe family, one of the leading kuge (court noble) lineages of Japan’s aristocracy.

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_69d889e2c2608190b762e76d9b2262f1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46e3ed8b08190a00efdad9740bf6f completed April 19, 2026, 5:55 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2757c7d1d88190aa97fa19408a2151 completed June 9, 2026, 12:01 a.m.
NEDg Description generation batch_6a275a7d33848190ba11aeb45c7e8b83 completed June 9, 2026, 12:12 a.m.
NED2 Entity disambiguation (via description) batch_6a275b11987081908ec648ce1eeceed3 completed June 9, 2026, 12:15 a.m.
Created at: April 10, 2026, 6:05 a.m.