Triple

T33252385
Position Surface form Disambiguated ID Type / Status
Subject Chiyoda, Tokyo E851284 entity
Predicate formedByMergerOf P77 FINISHED
Object Kojimachi Ward
Kojimachi Ward was a former administrative ward of Tokyo known for encompassing central government and business districts before being merged into modern Chiyoda Ward.
E2288137 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: Kojimachi Ward | Statement: [Chiyoda, Tokyo, formedByMergerOf, Kojimachi Ward]
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: Kojimachi Ward
Triple: [Chiyoda, Tokyo, formedByMergerOf, Kojimachi Ward]
Generated description
Kojimachi Ward was a former administrative ward of Tokyo known for encompassing central government and business districts before being merged into modern Chiyoda Ward.

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_69f34963135c819084e7f1d483421f00 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6db2f4b2081909fd2e59258927121 completed May 3, 2026, 5:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5a67a96f8c8190ab83bf9372e975e2 completed July 17, 2026, 5:34 p.m.
NEDg Description generation batch_6a5a684c57648190b7c505bfb60bfc25 completed July 17, 2026, 5:37 p.m.
NED2 Entity disambiguation (via description) batch_6a5a69da98408190867c1ab46b93e07f completed July 17, 2026, 5:43 p.m.
Created at: May 1, 2026, 1:31 a.m.