Triple

T18611918
Position Surface form Disambiguated ID Type / Status
Subject Qinhuangdao–Shenyang Railway E454912 entity
Predicate endPoint P390 FINISHED
Object Shenyang E20553 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: Shenyang | Statement: [Qinhuangdao–Shenyang Railway, endPoint, Shenyang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shenyang
Context triple: [Qinhuangdao–Shenyang Railway, endPoint, Shenyang]
  • A. Shenyang chosen
    Shenyang is a major industrial and historical city in northeastern China and the capital of Liaoning Province.
  • B. Dalian
    Dalian is a major port city in northeastern China known for its strategic location on the Liaodong Peninsula, maritime trade, and modern urban development.
  • C. Liaoyuan
    Liaoyuan is a prefecture-level city in northeastern China known for its coal mining history and location in the central part of Jilin Province.
  • D. Changchun
    Changchun is a major city in northeastern China that served as the capital of the Japanese puppet state of Manchukuo during the early 20th century.
  • E. Anshan
    Anshan was an ancient city and region in southwestern Iran that served as an early center of Elamite and later Achaemenid Persian power.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d8d38bbe7c8190bdec3138e7d413c9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54d01ebd08190b6e646e3a749d7f5 completed April 19, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a050389d4f481908463ea2501295b8b completed May 13, 2026, 11:04 p.m.
Created at: April 10, 2026, 11:45 a.m.