Triple

T29006480
Position Surface form Disambiguated ID Type / Status
Subject Yeosu Expo Station E736448 entity
Predicate formerName P65 FINISHED
Object Yeocheon Station
Yeocheon Station is the former name of Yeosu Expo Station, a railway station in Yeosu, South Korea that serves visitors to the Yeosu Expo site and the surrounding coastal city.
E2226723 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: Yeocheon Station | Statement: [Yeosu Expo Station, formerName, Yeocheon Station]
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: Yeocheon Station
Triple: [Yeosu Expo Station, formerName, Yeocheon Station]
Generated description
Yeocheon Station is the former name of Yeosu Expo Station, a railway station in Yeosu, South Korea that serves visitors to the Yeosu Expo site and the surrounding coastal city.

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_69f077eb81e88190ad9ff62cbb9f555e completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f65fc08c78819086abfcb2c02af163 completed May 2, 2026, 8:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40822829e881909e53dd7d47d72904 completed June 28, 2026, 2:08 a.m.
NEDg Description generation batch_6a408301ac7481909a67b2b663296357 completed June 28, 2026, 2:12 a.m.
NED2 Entity disambiguation (via description) batch_6a4083b93a508190819fe83da97374f7 completed June 28, 2026, 2:15 a.m.
Created at: April 28, 2026, 9:38 a.m.