Triple
T38270821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wo Hop Shek Public Cemetery |
E1021202
|
entity |
| Predicate | isMajorCemeteryIn |
P124531
|
FINISHED |
| Object | Hong Kong |
—
|
NE NERFINISHED |
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: Hong Kong | Statement: [Wo Hop Shek Public Cemetery, isMajorCemeteryIn, Hong Kong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorCemeteryIn Context triple: [Wo Hop Shek Public Cemetery, isMajorCemeteryIn, Hong Kong]
-
A.
isLargestCemeteryOf
Indicates that one cemetery is the largest (by size, capacity, or another defined measure) among all cemeteries associated with a given place or entity.
-
B.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
C.
usedAsMainCemeteryOf
Indicates that one location functions as the primary burial ground or principal cemetery serving another entity (such as a settlement, community, or institution).
-
D.
isOneOfLargestCemeteriesIn
chosen
Indicates that a cemetery ranks among the largest cemeteries located within a specified area or region.
-
E.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 3, 2026, 4:30 p.m.