Triple

T29595592
Position Surface form Disambiguated ID Type / Status
Subject Mount Kumotori E754285 entity
Predicate nameRomanization P2508 FINISHED
Object Kumotori-yama
Kumotori-yama is a prominent mountain on the border of Tokyo, Saitama, and Yamanashi Prefectures in Japan, known as the highest peak in Tokyo and a popular hiking destination.
E2030726 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: Kumotori-yama | Statement: [Mount Kumotori, nameRomanization, Kumotori-yama]
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: Kumotori-yama
Triple: [Mount Kumotori, nameRomanization, Kumotori-yama]
Generated description
Kumotori-yama is a prominent mountain on the border of Tokyo, Saitama, and Yamanashi Prefectures in Japan, known as the highest peak in Tokyo and a popular hiking destination.

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_69f0ef836ac88190bd809dc58b5ec907 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f66db7c2e08190a438ce9865666020 completed May 2, 2026, 9:33 p.m.
NED1 Entity disambiguation (via context triple) batch_6a34d239177c8190b740a9c3804e4484 completed June 19, 2026, 5:23 a.m.
NEDg Description generation batch_6a34d3bdb6808190967b4c67d5a3af66 completed June 19, 2026, 5:29 a.m.
NED2 Entity disambiguation (via description) batch_6a34d46b4a4081909c03beb97142b28e completed June 19, 2026, 5:32 a.m.
Created at: April 28, 2026, 6:17 p.m.