Triple
T33796280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taikoo Shing |
E866082
|
entity |
| Predicate | servedByMTRStation |
P28508
|
FINISHED |
| Object | Tai Koo station |
—
|
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: Tai Koo station | Statement: [Taikoo Shing, servedByMTRStation, Tai Koo station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByMTRStation Context triple: [Taikoo Shing, servedByMTRStation, Tai Koo station]
-
A.
subwayStation
chosen
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
-
B.
connectsToMetroLineAt
Indicates that one location or transportation facility is directly linked or provides access to a specific metro line at a particular point.
-
C.
servedByRailwayTerminus
Indicates that a place or location is provided rail transport services by a specific railway terminus.
-
D.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
E.
monorailStation
Indicates that an entity functions as a station or stop specifically for a monorail transit system.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 1, 2026, 1:46 a.m.