Triple

T38603939
Position Surface form Disambiguated ID Type / Status
Subject Akō Domain E934292 entity
Predicate daimyō P169391 FINISHED
Object Asano Nagahide
Asano Nagahide was a Japanese feudal lord of the Edo period who ruled the Akō Domain and belonged to the Asano clan of daimyō.
E2282354 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: Asano Nagahide | Statement: [Akō Domain, daimyō, Asano Nagahide]
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: Asano Nagahide
Triple: [Akō Domain, daimyō, Asano Nagahide]
Generated description
Asano Nagahide was a Japanese feudal lord of the Edo period who ruled the Akō Domain and belonged to the Asano clan of daimyō.

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_69f76ecc17688190b389b693a5927501 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcdbe798448190b0a4641c8c56ba74 completed May 7, 2026, 6:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a42158362248190aa60d7501b164af2 completed June 29, 2026, 6:49 a.m.
NEDg Description generation batch_6a4216b3e65081909579bc0e4fce5755 completed June 29, 2026, 6:54 a.m.
NED2 Entity disambiguation (via description) batch_6a4217369fbc8190bfbb799a7fbb79e6 completed June 29, 2026, 6:56 a.m.
Created at: May 3, 2026, 4:32 p.m.