Triple

T24645214
Position Surface form Disambiguated ID Type / Status
Subject Battle of Anegawa E610088 entity
Predicate belligerent P375 FINISHED
Object Asakura clan
The Asakura clan was a powerful samurai family of Japan’s Sengoku period, best known for its rule over Echizen Province and its downfall in conflicts against Oda Nobunaga.
E1746173 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: Asakura clan | Statement: [Battle of Anegawa, belligerent, Asakura clan]
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: Asakura clan
Triple: [Battle of Anegawa, belligerent, Asakura clan]
Generated description
The Asakura clan was a powerful samurai family of Japan’s Sengoku period, best known for its rule over Echizen Province and its downfall in conflicts against Oda Nobunaga.

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_69e2c4d350a481909170482bc2ce6af9 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f40f808a748190ab8ae16472daeabb completed May 1, 2026, 2:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a121e66e284819093df1feb202cd573 completed May 23, 2026, 9:38 p.m.
NEDg Description generation batch_6a121f2214c88190a68cd83be4196fc5 completed May 23, 2026, 9:41 p.m.
NED2 Entity disambiguation (via description) batch_6a121f96d69081909fa69572c9e3e1f8 completed May 23, 2026, 9:43 p.m.
Created at: April 18, 2026, 2:33 a.m.