Triple

T34745855
Position Surface form Disambiguated ID Type / Status
Subject Lung Cheung Road E1001633 entity
Predicate connectsTo P845 FINISHED
Object Ching Cheung Road
Ching Cheung Road is a major expressway in Hong Kong that forms part of Route 7, linking Kowloon to the New Territories and serving as a key east–west traffic corridor.
E2119394 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: Ching Cheung Road | Statement: [Lung Cheung Road, connectsTo, Ching Cheung Road]
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: Ching Cheung Road
Triple: [Lung Cheung Road, connectsTo, Ching Cheung Road]
Generated description
Ching Cheung Road is a major expressway in Hong Kong that forms part of Route 7, linking Kowloon to the New Territories and serving as a key east–west traffic corridor.

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_69f76db0367081909b57c50a7fb03025 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f779d317f88190bf3491fa92b555f8 completed May 3, 2026, 4:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37a89cb9b881909708b536ee827bae completed June 21, 2026, 9:02 a.m.
NEDg Description generation batch_6a37a9cd9850819094e07e59e8dedc96 completed June 21, 2026, 9:07 a.m.
NED2 Entity disambiguation (via description) batch_6a37abd05f4c819089833309fc436419 completed June 21, 2026, 9:16 a.m.
Created at: May 3, 2026, 3:59 p.m.