Triple
T33650978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiralty MTR station |
E862096
|
entity |
| Predicate | openedForSouthIslandLine |
P192796
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Admiralty MTR station, openedForSouthIslandLine, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForSouthIslandLine Context triple: [Admiralty MTR station, openedForSouthIslandLine, 2016]
-
A.
openedForIslandLine
Indicates that something (such as a facility, service, or route) was opened specifically to serve or operate on the Island Line.
-
B.
openedOnVictoriaLine
Indicates that something (such as a station or facility) began operation specifically on the Victoria Line.
-
C.
openedForBusService
Indicates that a facility, route, or location has begun operating and is available for use by public bus services.
-
D.
openedForCircleLine
Indicates that something (such as a station, section, or facility) was opened specifically for use by the Circle Line.
-
E.
openedOnCentralLine
Indicates that something was opened or began operating while located on or associated with the Central Line.
- F. None of above. chosen
Provenance (4 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
| PDg | Predicate description generation | batch_69fd2a2095f88190bfcbcb2973516ffc |
completed | May 8, 2026, 12:11 a.m. |
Created at: May 1, 2026, 1:42 a.m.