Triple

T25588075
Position Surface form Disambiguated ID Type / Status
Subject Katō Kiyomasa E641440 entity
Predicate heldTitle P8 FINISHED
Object daimyō of Higo Province
The daimyō of Higo Province was a powerful feudal lord in Japan’s Kyushu region who governed Higo (modern Kumamoto Prefecture) under the Tokugawa shogunate.
E1687847 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: daimyō of Higo Province | Statement: [Katō Kiyomasa, heldTitle, daimyō of Higo Province]
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: daimyō of Higo Province
Triple: [Katō Kiyomasa, heldTitle, daimyō of Higo Province]
Generated description
The daimyō of Higo Province was a powerful feudal lord in Japan’s Kyushu region who governed Higo (modern Kumamoto Prefecture) under the Tokugawa shogunate.

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_69e75dc42b588190a98b58e0df359674 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f96b32008190ad411ee7472c6b77 completed May 2, 2026, 1:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10b767d0788190820a893f7927ce3b completed May 22, 2026, 8:07 p.m.
NEDg Description generation batch_6a10b8652614819087580690269f6a3a completed May 22, 2026, 8:11 p.m.
NED2 Entity disambiguation (via description) batch_6a10b99e39b08190abbe927b4916c0ee completed May 22, 2026, 8:16 p.m.
Created at: April 21, 2026, 4:18 p.m.