Triple
T35170341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsz Ching Estate |
E1015528
|
entity |
| Predicate | hasBlockCount |
P92310
|
FINISHED |
| Object | 11 residential blocks |
—
|
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: 11 residential blocks | Statement: [Tsz Ching Estate, hasBlockCount, 11 residential blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBlockCount Context triple: [Tsz Ching Estate, hasBlockCount, 11 residential blocks]
-
A.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
B.
numberOfBlocks
chosen
Indicates the quantity of discrete block units associated with or contained by a given entity.
-
C.
hasBlockStatus
Indicates that one entity is currently blocked or restricted in its interaction or access relative to another entity.
-
D.
estimatedNumberOfBlocks
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
-
E.
hasSectionCount
Indicates that an entity is associated with a specific number of sections it contains or comprises.
- 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_69f78d3b0f0c81908e45789816ab70b4 |
completed | May 3, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.