Triple
T33650977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiralty MTR station |
E862096
|
entity |
| Predicate | openedForIslandLine |
P192727
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [Admiralty MTR station, openedForIslandLine, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForIslandLine Context triple: [Admiralty MTR station, openedForIslandLine, 1985]
-
A.
openedForCircleLine
Indicates that something (such as a station, section, or facility) was opened specifically for use by the Circle Line.
-
B.
openedForIND
Indicates that an entity has been opened or made available specifically for an Investigational New Drug (IND) application or process.
-
C.
openedOnDistrictAndCircleLines
Indicates that something (such as a station or section) was opened specifically on both the District and Circle railway lines.
-
D.
openedForTram
Indicates that something (such as a route, track, or facility) is available and in use for tram operations.
-
E.
openingLineStatus
Indicates the status or condition of an entity’s opening line, such as whether it exists, is valid, or meets a specified criterion.
- 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_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
| PDg | Predicate description generation | batch_69fd28379d2c8190903ba228ee1cc756 |
completed | May 8, 2026, 12:03 a.m. |
Created at: May 1, 2026, 1:42 a.m.