Triple

T28200427
Position Surface form Disambiguated ID Type / Status
Subject Summer Hill campus E716867 entity
Predicate locatedNear P294 FINISHED
Object Summer Hill railway station
Summer Hill railway station is a suburban train station in Sydney, Australia, serving the inner-west suburb of Summer Hill on the Main Suburban line.
E1809155 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: Summer Hill railway station | Statement: [Summer Hill campus, locatedNear, Summer Hill 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: Summer Hill railway station
Triple: [Summer Hill campus, locatedNear, Summer Hill railway station]
Generated description
Summer Hill railway station is a suburban train station in Sydney, Australia, serving the inner-west suburb of Summer Hill on the Main Suburban line.

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_69efd6b826908190857e6e7dad74ed93 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f642d510548190b9f34ed50d80f858 completed May 2, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15e6b50c18819099041cfd31f2a6d5 completed May 26, 2026, 6:30 p.m.
NEDg Description generation batch_6a15eec2ef9081908b5a99d7900eb82f completed May 26, 2026, 7:04 p.m.
NED2 Entity disambiguation (via description) batch_6a15f40d69c48190ab96b08d36dcd904 completed May 26, 2026, 7:27 p.m.
Created at: April 27, 2026, 10:31 p.m.