Triple

T28193932
Position Surface form Disambiguated ID Type / Status
Subject SR Co., Ltd. E716387 entity
Predicate operatesOn P23 FINISHED
Object Suseo High Speed Railway
Suseo High Speed Railway is a South Korean high-speed rail line connecting Seoul’s Suseo station with major southern cities, designed to reduce travel times and ease congestion on existing routes.
E1826894 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: Suseo High Speed Railway | Statement: [SR Co., Ltd., operatesOn, Suseo High Speed Railway]
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: Suseo High Speed Railway
Triple: [SR Co., Ltd., operatesOn, Suseo High Speed Railway]
Generated description
Suseo High Speed Railway is a South Korean high-speed rail line connecting Seoul’s Suseo station with major southern cities, designed to reduce travel times and ease congestion on existing routes.

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_69efd6b612f48190a72012b520afbd10 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f642cf92d88190bdb919fc9fb18c2b completed May 2, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cc358df5c819099e15c1b4b2041d2 completed May 31, 2026, 11:25 p.m.
NEDg Description generation batch_6a1cc3c360808190a2961b3e0a3c839f completed May 31, 2026, 11:26 p.m.
NED2 Entity disambiguation (via description) batch_6a1cc45223488190a914244c6245a86f completed May 31, 2026, 11:29 p.m.
Created at: April 27, 2026, 10:26 p.m.