Triple
T3258266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chennai Metro |
E68347
|
entity |
| Predicate | openingDateOfFirstSection |
P20181
|
FINISHED |
| Object | 2015-06-29 |
—
|
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: 2015-06-29 | Statement: [Chennai Metro, openingDateOfFirstSection, 2015-06-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateOfFirstSection Context triple: [Chennai Metro, openingDateOfFirstSection, 2015-06-29]
-
A.
firstSectionOpened
chosen
Indicates that the initial section in a sequence or structure has been opened or activated.
-
B.
openingDateOfFirstSpan
Indicates the date on which the first span (e.g., of a structure or project) was initially opened or put into service.
-
C.
firstSectionOpenedBetween
Indicates that the first section was opened at some point within a specified time interval or between two defined events.
-
D.
openingDateLine16
Indicates the date on which line 16 was officially opened or began operation.
-
E.
openedSectionBetween
Indicates that one entity has created or established an open section, gap, or interval between itself and another entity.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf6a46448190a7fa0ca83fa096f8 |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.