Triple

T31276694
Position Surface form Disambiguated ID Type / Status
Subject Changsha railway network E797539 entity
Predicate hasMajorStation P1071 FINISHED
Object Changsha North railway station
Changsha North railway station is a key passenger and transport hub in Changsha, Hunan Province, serving major regional and national rail routes.
E1960110 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: Changsha North railway station | Statement: [Changsha railway network, hasMajorStation, Changsha North railway 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: Changsha North railway station
Triple: [Changsha railway network, hasMajorStation, Changsha North railway station]
Generated description
Changsha North railway station is a key passenger and transport hub in Changsha, Hunan Province, serving major regional and national rail 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_69f224def9088190a37034eab3daf57f completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69dd274688190a82d7a57a0c73b3b completed May 3, 2026, 12:58 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2ad2222c7c819089584ba33a3e32bc completed June 11, 2026, 3:20 p.m.
NEDg Description generation batch_6a2ad61d68288190a6cdfc1131501945 completed June 11, 2026, 3:37 p.m.
NED2 Entity disambiguation (via description) batch_6a2ae15e581c81909bb1cd58b50096d7 completed June 11, 2026, 4:25 p.m.
Created at: April 29, 2026, 9:13 p.m.