Triple
T16701885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbai–Pune route |
E405872
|
entity |
| Predicate | openedExpresswayYear |
P51556
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Mumbai–Pune route, openedExpresswayYear, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedExpresswayYear Context triple: [Mumbai–Pune route, openedExpresswayYear, 2002]
-
A.
openedToTrafficInYear
Indicates the year in which something, typically a transportation facility or route, was first officially opened for public traffic use.
-
B.
openingYearForModernHighway
chosen
Indicates the calendar year in which a modern highway was first opened to traffic or put into official operation.
-
C.
openedAsExpresswaySection
Indicates that a particular section of roadway was inaugurated and began operation specifically as an expressway segment.
-
D.
roadTunnelOpeningYear
Indicates the calendar year in which a road tunnel was officially opened for use.
-
E.
openedForYearRoundTraffic
Indicates that something has been made accessible and usable for traffic throughout the entire year, without seasonal closures.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e383326d7081909ef4c3b724876513 |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.