Triple
T37313475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacob Circle–Wadala–Chembur corridor |
E926267
|
entity |
| Predicate | openingDateFullLine |
P194042
|
FINISHED |
| Object | 2019-03-03 |
—
|
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: 2019-03-03 | Statement: [Jacob Circle–Wadala–Chembur corridor, openingDateFullLine, 2019-03-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateFullLine Context triple: [Jacob Circle–Wadala–Chembur corridor, openingDateFullLine, 2019-03-03]
-
A.
openingDateLineC
Indicates the calendar date on which entity C is opened, initiated, or begins operation.
-
B.
openingDateLineB
Indicates the date on which line B is officially opened or begins operation.
-
C.
openingDateLineA
Indicates the date on which Line A officially began operating or was opened.
-
D.
openingDateAsThroughLine
Indicates that the opening date is used as a continuous reference or organizing thread linking related events, records, or states over time.
-
E.
openingDateLine10
Indicates the date on which line 10 (e.g., a specific route, service, or infrastructure line) was officially opened or began operation.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: May 3, 2026, 4:16 p.m.