Triple
T28158700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwarka Sector 21 |
E714827
|
entity |
| Predicate | blueLineExtensionOpening |
P100450
|
FINISHED |
| Object | 30 October 2010 |
—
|
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: 30 October 2010 | Statement: [Dwarka Sector 21, blueLineExtensionOpening, 30 October 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blueLineExtensionOpening Context triple: [Dwarka Sector 21, blueLineExtensionOpening, 30 October 2010]
-
A.
blueLineOpeningDate
Indicates the date on which the Blue Line was officially opened or began operation.
-
B.
northLineExtensionOpeningDate
Indicates the date on which the extension of the North Line officially opened for service.
-
C.
greenLineOpening
Indicates the event or point in time when a green-colored transit line (such as a subway, tram, or rail line) begins operation or is officially opened.
-
D.
purpleLineOpeningDate
Indicates the date on which the Purple Line officially began operation or service.
-
E.
blueLineServiceBegan
chosen
Indicates that service on the Blue Line began operating at a specified time or event.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641e9eac08190976874fc569b4a63 |
completed | May 2, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:04 p.m.