Triple

T34822096
Position Surface form Disambiguated ID Type / Status
Subject Ashikaga Yoshiteru E1003806 entity
Predicate opponent P437 FINISHED
Object Miyoshi Nagayoshi
Miyoshi Nagayoshi was a powerful Sengoku-period daimyō and head of the Miyoshi clan who dominated the politics of the Ashikaga shogunate in the mid-16th century.
E2283785 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: Miyoshi Nagayoshi | Statement: [Ashikaga Yoshiteru, opponent, Miyoshi Nagayoshi]
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: Miyoshi Nagayoshi
Triple: [Ashikaga Yoshiteru, opponent, Miyoshi Nagayoshi]
Generated description
Miyoshi Nagayoshi was a powerful Sengoku-period daimyō and head of the Miyoshi clan who dominated the politics of the Ashikaga shogunate in the mid-16th century.

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_69f76db717088190811b4e744610f37d completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77adeac048190bbe22f1b663009d5 completed May 3, 2026, 4:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a42e078c0848190b078c9c41fc66b17 completed June 29, 2026, 9:15 p.m.
NEDg Description generation batch_6a42e148d1708190b1b5bef0ef2b9078 completed June 29, 2026, 9:19 p.m.
NED2 Entity disambiguation (via description) batch_6a42ec8ba09c819095262fda3589b6ad completed June 29, 2026, 10:07 p.m.
Created at: May 3, 2026, 4 p.m.