Triple

T14251018
Position Surface form Disambiguated ID Type / Status
Subject Sheung Shui E353261 entity
Predicate near P350 FINISHED
Object Lok Ma Chau E563728 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: Lok Ma Chau | Statement: [Sheung Shui, near, Lok Ma Chau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lok Ma Chau
Context triple: [Sheung Shui, near, Lok Ma Chau]
  • A. Sha Tau Kok
    Sha Tau Kok is a frontier town in northeastern Hong Kong known for its restricted border area status and proximity to the boundary with mainland China.
  • B. Tai Khuen
    Tai Khuen is a Tai ethnic group and language primarily associated with the Kengtung region of eastern Myanmar.
  • C. Tai Hang
    Tai Hang is a residential and dining neighborhood on Hong Kong Island known for its narrow streets, local eateries, and the annual Fire Dragon Dance during the Mid-Autumn Festival.
  • D. Ma Wan
    Ma Wan is a small island in Hong Kong known for its residential developments, historic fishing village, and attractions like Noah’s Ark near the Tsing Ma Bridge.
  • E. Lok Ma Chau control point chosen
    Lok Ma Chau Control Point is a major land border crossing between Hong Kong and mainland China, serving as a key passenger and cargo gateway near Shenzhen.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8278c43e08190824146f4632b89a5 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6296f9d0819086f62f525d07eb12 completed April 14, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd325815d48190b070866f41986847 completed May 8, 2026, 12:46 a.m.
Created at: April 10, 2026, 1:08 a.m.