Triple
T27477155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karkarduma metro station |
E693493
|
entity |
| Predicate | openedOnPinkLine |
P174679
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Karkarduma metro station, openedOnPinkLine, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedOnPinkLine Context triple: [Karkarduma metro station, openedOnPinkLine, 2018]
-
A.
openedOnBlueLine
Indicates that an entity was opened, initiated, or began operation specifically on the blue line (e.g., a blue-designated route, track, or service line).
-
B.
openedAsRedLineStation
Indicates that a station began operation specifically as part of the Red Line when it first opened.
-
C.
openedAsMetrolinkLine
Indicates that a railway line or route was inaugurated or began operation specifically as part of the Metrolink network.
-
D.
openedAsCurrentOrangeLineTerminus
Indicates that a location began operation specifically as the then-current terminus (end station) of the Orange Line.
-
E.
openedOnDistrictAndCircleLines
Indicates that something (such as a station or section) was opened specifically on both the District and Circle railway lines.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 27, 2026, 12:57 p.m.