Triple
T12953256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wong Tai Sin District |
E309944
|
entity |
| Predicate | religiousTraditionAtTemple |
P15993
|
FINISHED |
| Object | Taoism |
—
|
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: Taoism | Statement: [Wong Tai Sin District, religiousTraditionAtTemple, Taoism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousTraditionAtTemple Context triple: [Wong Tai Sin District, religiousTraditionAtTemple, Taoism]
-
A.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
B.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
C.
templePractice
Indicates a religious or ritual activity that is performed within or in connection with a temple.
-
D.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
-
E.
isPlaceOfWorshipFor
chosen
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:44 p.m.