Triple

T34722687
Position Surface form Disambiguated ID Type / Status
Subject Hung Hom Estate E1000960 entity
Predicate hasNearbyRoad P11435 FINISHED
Object Ma Tau Wai Road
Ma Tau Wai Road is a major thoroughfare in Kowloon, Hong Kong, running through residential and commercial districts including the area around Hung Hom Estate.
E2113557 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: Ma Tau Wai Road | Statement: [Hung Hom Estate, hasNearbyRoad, Ma Tau Wai Road]
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: Ma Tau Wai Road
Triple: [Hung Hom Estate, hasNearbyRoad, Ma Tau Wai Road]
Generated description
Ma Tau Wai Road is a major thoroughfare in Kowloon, Hong Kong, running through residential and commercial districts including the area around Hung Hom Estate.

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_69f76daeb6e48190a4c9a6b0edc80f72 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f779a436c88190a1f3aceab640202d completed May 3, 2026, 4:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a376f9652448190a5d92938e2b53ef3 completed June 21, 2026, 4:59 a.m.
NEDg Description generation batch_6a3770687b8c8190b271515f54eed3b8 completed June 21, 2026, 5:02 a.m.
NED2 Entity disambiguation (via description) batch_6a37719691ac8190bc3ad20af00b1cf2 completed June 21, 2026, 5:07 a.m.
Created at: May 3, 2026, 3:59 p.m.