Triple
T27081323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern District |
E685603
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object |
Chi Fu Fa Yuen
Chi Fu Fa Yuen is a large private residential estate in Hong Kong known for its multiple high-rise towers and self-contained community facilities.
|
E1755305
|
NE 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: Chi Fu Fa Yuen | Statement: [Southern District, contains, Chi Fu Fa Yuen]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Chi Fu Fa Yuen Triple: [Southern District, contains, Chi Fu Fa Yuen]
Generated description
Chi Fu Fa Yuen is a large private residential estate in Hong Kong known for its multiple high-rise towers and self-contained community facilities.
Provenance (5 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623417cfc81908943186b0b8c3e7b |
completed | May 2, 2026, 4:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a123ae02598819095a9471e89a420c3 |
completed | May 23, 2026, 11:40 p.m. |
| NEDg | Description generation | batch_6a123bead64881909ae531a7adbaafe1 |
completed | May 23, 2026, 11:44 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a123c4f67388190a885b5ce89f9baa6 |
completed | May 23, 2026, 11:46 p.m. |
Created at: April 27, 2026, 8:34 a.m.