Triple

T19117242
Position Surface form Disambiguated ID Type / Status
Subject Line 6 E467936 entity
Predicate hasStation P35 FINISHED
Object Yaksu Station
Yaksu Station is a subway station in Seoul, South Korea, serving as an interchange between Seoul Subway Line 3 and Line 6.
E2295399 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: Yaksu Station | Statement: [Line 6, hasStation, Yaksu 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: Yaksu Station
Triple: [Line 6, hasStation, Yaksu Station]
Generated description
Yaksu Station is a subway station in Seoul, South Korea, serving as an interchange between Seoul Subway Line 3 and Line 6.

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_69d8dd06a26481908039e2a1bae8c597 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e399a6d8819090a9501ff1637b9d completed April 20, 2026, 8:28 a.m.
NED1 Entity disambiguation (via context triple) batch_6a7d4ca5ffdc819080909453c4236257 completed Aug. 13, 2026, 4:48 a.m.
NEDg Description generation batch_6a7d4dabf8ac819088249a69b95205bb completed Aug. 13, 2026, 4:53 a.m.
NED2 Entity disambiguation (via description) batch_6a7d4df9838c81909a3733ffd9935680 completed Aug. 13, 2026, 4:54 a.m.
Created at: April 10, 2026, 12:05 p.m.