Triple

T28804861
Position Surface form Disambiguated ID Type / Status
Subject Iruma E727343 entity
Predicate hasAttraction P105 FINISHED
Object Johnson Town
Johnson Town is a retro-style residential and commercial district in Iruma, Saitama Prefecture, known for its American-inspired townscape of low-rise wooden houses, cafes, and shops.
E1838224 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: Johnson Town | Statement: [Iruma, hasAttraction, Johnson Town]
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: Johnson Town
Triple: [Iruma, hasAttraction, Johnson Town]
Generated description
Johnson Town is a retro-style residential and commercial district in Iruma, Saitama Prefecture, known for its American-inspired townscape of low-rise wooden houses, cafes, and shops.

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_69f0319c38948190bca746ad60fd25ba completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f658aceef4819087f7b9298bc53cd3 completed May 2, 2026, 8:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24d3ebf40881908d0f7bbedb62f137 completed June 7, 2026, 2:14 a.m.
NEDg Description generation batch_6a24d7f48c948190b614235728863682 completed June 7, 2026, 2:31 a.m.
NED2 Entity disambiguation (via description) batch_6a24da02305081908055992ee6c0fc56 completed June 7, 2026, 2:40 a.m.
Created at: April 28, 2026, 6:28 a.m.