Triple
T3162033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Library station |
E66122
|
entity |
| Predicate | openingDateLine16 |
P46433
|
FINISHED |
| Object | 2020-12-31 |
—
|
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: 2020-12-31 | Statement: [National Library station, openingDateLine16, 2020-12-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateLine16 Context triple: [National Library station, openingDateLine16, 2020-12-31]
-
A.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
B.
firstLineOpeningDate
Indicates the date on which the first line in a system, network, or service was officially opened or began operation.
-
C.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
D.
line13OpeningDate
Indicates the date on which line 13 was officially opened or began operation.
-
E.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada618b9b88190afaa6d47dcad9f2c |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:06 p.m.