Triple
T17859186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Metro Silver Line |
E446020
|
entity |
| Predicate | phase2Opened |
P40333
|
FINISHED |
| Object | 2022-11-15 |
—
|
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: 2022-11-15 | Statement: [Washington Metro Silver Line, phase2Opened, 2022-11-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phase2Opened Context triple: [Washington Metro Silver Line, phase2Opened, 2022-11-15]
-
A.
phase1OpeningDate
Indicates the date on which the first phase of a project, development, or initiative is officially opened or begins operation.
-
B.
openingDatePhase2
chosen
Indicates the date on which the second phase of a project, process, or facility is scheduled to begin or officially open.
-
C.
phase2Purpose
Indicates the specific intended goal, function, or outcome associated with the second phase of a process or project.
-
D.
phasedOpening
Indicates that the opening or launch of something occurs in multiple planned stages or phases rather than all at once.
-
E.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4978e68ec8190a4306f7b7bb058d7 |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.