Triple

T38512188
Position Surface form Disambiguated ID Type / Status
Subject Josiah Conder E921941 entity
Predicate employer P7 FINISHED
Object Kobu Daigakko
Kobu Daigakko was a pioneering late-19th-century Japanese engineering and architecture school that played a key role in training modern technical experts during the Meiji era.
E2190317 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: Kobu Daigakko | Statement: [Josiah Conder, employer, Kobu Daigakko]
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: Kobu Daigakko
Triple: [Josiah Conder, employer, Kobu Daigakko]
Generated description
Kobu Daigakko was a pioneering late-19th-century Japanese engineering and architecture school that played a key role in training modern technical experts during the Meiji era.

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_69f76ea3c5448190aa7002fc1ba3f874 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcd28d33b08190a0f6ff47be5eaaae completed May 7, 2026, 5:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5c54f36dd88190bded083391347fc8 completed July 19, 2026, 4:39 a.m.
NEDg Description generation batch_6a5c57038c04819092d60ad1430f8f25 completed July 19, 2026, 4:48 a.m.
NED2 Entity disambiguation (via description) batch_6a5c5776f914819091f3538bbd406bdd completed July 19, 2026, 4:49 a.m.
Created at: May 3, 2026, 4:32 p.m.