Triple
T35317685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsz Oi Court |
E1019948
|
entity |
| Predicate | nearbyPublicHousing |
P103472
|
FINISHED |
| Object | Tsz Wan Shan Estate |
—
|
NE NERFINISHED |
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 Wan Shan Estate | Statement: [Tsz Oi Court, nearbyPublicHousing, Tsz Wan Shan Estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyPublicHousing Context triple: [Tsz Oi Court, nearbyPublicHousing, Tsz Wan Shan Estate]
-
A.
nearbyEstate
chosen
Indicates that one estate is located close to another estate in physical space.
-
B.
isPublicHousing
Indicates that the entity is designated as government-provided or subsidized residential housing intended for public use.
-
C.
nearbyFindHousedAt
Indicates that an entity finds or locates something that is housed or stored at a nearby place or facility.
-
D.
hasPublicHousing
Indicates that a location or jurisdiction provides or contains government-funded residential housing available to the public.
-
E.
hasPublicHousingAuthority
Indicates that an entity is associated with, governed by, or served by a specific public housing authority.
- F. None of above.
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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: May 3, 2026, 4:03 p.m.