Triple

T24145131
Position Surface form Disambiguated ID Type / Status
Subject Tsukishima E598357 entity
Predicate hasStreet P959 FINISHED
Object Tsukishima Monja Street
Tsukishima Monja Street is a famous food alley in Tokyo known for its dense concentration of restaurants specializing in monjayaki, a local savory pan-fried dish.
E1628357 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: Tsukishima Monja Street | Statement: [Tsukishima, hasStreet, Tsukishima Monja Street]
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: Tsukishima Monja Street
Triple: [Tsukishima, hasStreet, Tsukishima Monja Street]
Generated description
Tsukishima Monja Street is a famous food alley in Tokyo known for its dense concentration of restaurants specializing in monjayaki, a local savory pan-fried dish.

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_69e288c9e488819093dd1acd91b08b8a completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1e00a37b881909e31f85a667e6d83 completed April 29, 2026, 10:40 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fc9a489e8819088579c8423725b8e completed May 22, 2026, 3:12 a.m.
NEDg Description generation batch_6a0fcb0d718c81909c02cea23a2bffdc completed May 22, 2026, 3:18 a.m.
NED2 Entity disambiguation (via description) batch_6a0fcbe802788190b1383ce61a5e0cc4 completed May 22, 2026, 3:22 a.m.
Created at: April 17, 2026, 11:29 p.m.