Triple

T27299814
Position Surface form Disambiguated ID Type / Status
Subject Chai Wan E688873 entity
Predicate hasPublicHousingEstate P12192 FINISHED
Object Tsui Wan Estate
Tsui Wan Estate is a public housing estate in the Chai Wan area of Hong Kong, providing affordable residential accommodation in a high-density urban setting.
E1784547 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: Tsui Wan Estate | Statement: [Chai Wan, hasPublicHousingEstate, Tsui Wan Estate]
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: Tsui Wan Estate
Triple: [Chai Wan, hasPublicHousingEstate, Tsui Wan Estate]
Generated description
Tsui Wan Estate is a public housing estate in the Chai Wan area of Hong Kong, providing affordable residential accommodation in a high-density urban setting.

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_69ef355a96308190a2bed991525fb278 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f62783adb48190a0db49be8167fb3d completed May 2, 2026, 4:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12da6b0288819089e4b2a425670b4b completed May 24, 2026, 11 a.m.
NEDg Description generation batch_6a12ddd102ac8190838e6ee34ebbf295 completed May 24, 2026, 11:15 a.m.
NED2 Entity disambiguation (via description) batch_6a12de788ac081908ee34621742eeef5 completed May 24, 2026, 11:18 a.m.
Created at: April 27, 2026, 11:21 a.m.