Triple
T35170361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsz Ching Estate |
E1015528
|
entity |
| Predicate | hasTargetResidents |
P99295
|
FINISHED |
| Object | low-income residents |
—
|
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: low-income residents | Statement: [Tsz Ching Estate, hasTargetResidents, low-income residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetResidents Context triple: [Tsz Ching Estate, hasTargetResidents, low-income residents]
-
A.
intendedResidents
chosen
Indicates the people or entities for whom a place, dwelling, or facility is designed or meant to be occupied by.
-
B.
hasResidentPopulation
Indicates that a place or administrative area has a population of people who live there permanently or for an extended period.
-
C.
hasTargetVisitors
Indicates that something is intended or designed to be visited by a specific group of people as its primary audience or users.
-
D.
inhabitantsServed
Indicates the relationship in which a service, facility, or resource provides for or meets the needs of a specified group of inhabitants.
-
E.
hasNonHumanResident
Indicates that a place or location is inhabited or occupied by one or more non-human entities.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:02 p.m.