Triple

T35589945
Position Surface form Disambiguated ID Type / Status
Subject Tsing Yi Promenade E1028468 entity
Predicate isPartOf P10 FINISHED
Object Tsing Yi waterfront
Tsing Yi waterfront is a scenic coastal area on Tsing Yi Island in Hong Kong featuring promenades, recreational spaces, and views over the surrounding harbor.
E2213948 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: Tsing Yi waterfront | Statement: [Tsing Yi Promenade, isPartOf, Tsing Yi waterfront]
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: Tsing Yi waterfront
Triple: [Tsing Yi Promenade, isPartOf, Tsing Yi waterfront]
Generated description
Tsing Yi waterfront is a scenic coastal area on Tsing Yi Island in Hong Kong featuring promenades, recreational spaces, and views over the surrounding harbor.

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_69f76e0495a081909beced418558c0b4 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79e8a9aec8190b78a30129a576605 completed May 3, 2026, 7:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3f69ef12b48190a1373909899f24f1 completed June 27, 2026, 6:13 a.m.
NEDg Description generation batch_6a3f6b68b16c819098b8a23407c6de19 completed June 27, 2026, 6:19 a.m.
NED2 Entity disambiguation (via description) batch_6a3f6bfc11b881909dcb875cc92f5535 completed June 27, 2026, 6:21 a.m.
Created at: May 3, 2026, 4:05 p.m.