Triple
T12953232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wong Tai Sin District |
E309944
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Tsz Man Estate |
E1016986
|
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: Tsz Man Estate | Statement: [Wong Tai Sin District, contains, Tsz Man Estate]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tsz Man Estate Context triple: [Wong Tai Sin District, contains, Tsz Man Estate]
-
A.
Tsz Man Estate
chosen
Tsz Man Estate is a public housing estate located in the Wong Tai Sin district of Kowloon, Hong Kong.
-
B.
Tsz Lok Estate
Tsz Lok Estate is a public housing estate located in the Wong Tai Sin district of Kowloon, Hong Kong.
-
C.
Tsz Hong Estate
Tsz Hong Estate is a public housing estate located in the Wong Tai Sin district of Kowloon, Hong Kong.
-
D.
Tsz Shan Estate
Tsz Shan Estate is a public housing estate located in the Wong Tai Sin district of Hong Kong.
-
E.
Tsz Wan Shan Estate
Tsz Wan Shan Estate is a large public housing estate in Hong Kong known for its dense residential blocks and hillside location in the Wong Tai Sin District.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e1edcdc8190a702c2a5ea58cc67 |
completed | April 10, 2026, 10:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7396b901c81908bfac5b40e3caed4 |
completed | May 3, 2026, 12:02 p.m. |
Created at: April 9, 2026, 5:44 p.m.