Triple

T35488968
Position Surface form Disambiguated ID Type / Status
Subject Sau Mau Ping E1025675 entity
Predicate hasPublicHousingEstate P12192 FINISHED
Object Sau Mau Ping Estate
Sau Mau Ping Estate is a large public housing complex in Sau Mau Ping, Kwun Tong, Hong Kong, providing affordable residential units to local residents.
E2157949 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: Sau Mau Ping Estate | Statement: [Sau Mau Ping, hasPublicHousingEstate, Sau Mau Ping 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: Sau Mau Ping Estate
Triple: [Sau Mau Ping, hasPublicHousingEstate, Sau Mau Ping Estate]
Generated description
Sau Mau Ping Estate is a large public housing complex in Sau Mau Ping, Kwun Tong, Hong Kong, providing affordable residential units to local residents.

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_69f76dfbcdd881908c7b0b6bc502252b completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7972ba73481909b8a8a8f2473746c completed May 3, 2026, 6:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a389bffe5d081909f4917c712268c2c completed June 22, 2026, 2:20 a.m.
NEDg Description generation batch_6a389d901c048190af8cbb4eb5fca156 completed June 22, 2026, 2:27 a.m.
NED2 Entity disambiguation (via description) batch_6a389e5407b48190a8f1610e6ba216b4 completed June 22, 2026, 2:30 a.m.
Created at: May 3, 2026, 4:04 p.m.