Triple
T34722656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hung Hom Estate |
E1000960
|
entity |
| Predicate | publicHousingCategory |
P160606
|
FINISHED |
| Object | rental housing |
—
|
LITERAL 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: rental housing | Statement: [Hung Hom Estate, publicHousingCategory, rental housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicHousingCategory Context triple: [Hung Hom Estate, publicHousingCategory, rental housing]
-
A.
realEstateCategory
Indicates the classification of a property into a specific type or category within real estate (e.g., residential, commercial, industrial).
-
B.
notPublicHousingEstate
Indicates that a given housing-related entity is explicitly classified as not being a public housing estate.
-
C.
isPublicHousing
chosen
Indicates that the entity is designated as government-provided or subsidized residential housing intended for public use.
-
D.
propertyTypeCommon
Indicates that two or more entities share the same general category or type of property.
-
E.
propertyType_id
Indicates a relationship that specifies the type or category of a property associated with an entity.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 3, 2026, 3:59 p.m.