Triple

T35756052
Position Surface form Disambiguated ID Type / Status
Subject Alishan Forest Railway E1033447 entity
Predicate hasBranchLine P1185 FINISHED
Object Zhushan Line
The Zhushan Line is a scenic mountain branch of Taiwan’s Alishan Forest Railway, known for its steep climbs and popular sunrise-viewing journeys above the clouds.
E2157126 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: Zhushan Line | Statement: [Alishan Forest Railway, hasBranchLine, Zhushan Line]
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: Zhushan Line
Triple: [Alishan Forest Railway, hasBranchLine, Zhushan Line]
Generated description
The Zhushan Line is a scenic mountain branch of Taiwan’s Alishan Forest Railway, known for its steep climbs and popular sunrise-viewing journeys above the clouds.

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_69f76e1262f48190a313318665acc189 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a19b531481909ced9ab9b852f284 completed May 3, 2026, 7:27 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3891585a2081908d594dc0e7a57fde completed June 22, 2026, 1:35 a.m.
NEDg Description generation batch_6a38959f0f008190b246c9a584895e0b completed June 22, 2026, 1:53 a.m.
NED2 Entity disambiguation (via description) batch_6a3895fe02c48190a62e68f6ec336881 completed June 22, 2026, 1:55 a.m.
Created at: May 3, 2026, 4:06 p.m.