Triple
T12229615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lan Kwai Fong |
E291439
|
entity |
| Predicate | previousPrimaryUse |
P76363
|
FINISHED |
| Object | residential area |
—
|
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: residential area | Statement: [Lan Kwai Fong, previousPrimaryUse, residential area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPrimaryUse Context triple: [Lan Kwai Fong, previousPrimaryUse, residential area]
-
A.
formerPrimaryUse
chosen
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
-
B.
originalPrimaryUse
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
C.
laterPrimarilyUsedFor
Indicates that something was initially used for one purpose but, at a later time, came to be used mainly for another specified purpose.
-
D.
regionPrimaryUse
Indicates the main functional purpose or dominant activity for which a region is used.
-
E.
terminal1PrimaryUse
Indicates the main or predominant function or purpose for which terminal 1 is used.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.