Triple

T25519954
Position Surface form Disambiguated ID Type / Status
Subject Konishi Yukinaga E639618 entity
Predicate domain P87 FINISHED
Object Uto, Higo Province
Uto, Higo Province was a feudal domain in early modern Japan located in present-day Kumamoto Prefecture, historically governed by samurai lords such as Konishi Yukinaga.
E1684966 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: Uto, Higo Province | Statement: [Konishi Yukinaga, domain, Uto, 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: Uto, Higo Province
Triple: [Konishi Yukinaga, domain, Uto, Higo Province]
Generated description
Uto, Higo Province was a feudal domain in early modern Japan located in present-day Kumamoto Prefecture, historically governed by samurai lords such as Konishi Yukinaga.

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_69e75dbe32e48190a62d749a0ff2a96a completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f8353d6c81908dd21e9e867d3753 completed May 2, 2026, 1:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10ad84d02c819095c24b97d7121183 completed May 22, 2026, 7:24 p.m.
NEDg Description generation batch_6a10af1c3da4819081cb3a843a9841d6 completed May 22, 2026, 7:31 p.m.
NED2 Entity disambiguation (via description) batch_6a10af914a4481909fad4723d5975df5 completed May 22, 2026, 7:33 p.m.
Created at: April 21, 2026, 2:59 p.m.