Triple
T3695190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurugram |
E78440
|
entity |
| Predicate | connectedBy |
P37
|
FINISHED |
| Object | Delhi Metro |
E19472
|
NE 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: Delhi Metro | Statement: [Gurugram, connectedBy, Delhi Metro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Delhi Metro Context triple: [Gurugram, connectedBy, Delhi Metro]
-
A.
Delhi Metro
chosen
Delhi Metro is a rapid transit system serving Delhi and its surrounding metropolitan region, known for its extensive network, modern infrastructure, and role in easing urban congestion.
-
B.
Mumbai Metro
Mumbai Metro is a rapid transit system serving the Mumbai metropolitan region, designed to alleviate congestion and complement the city’s suburban railway network.
-
C.
Kolkata Metro
Kolkata Metro is India’s oldest rapid transit system, serving as a major urban rail network for the city of Kolkata and its surrounding areas.
-
D.
Lucknow Metro
Lucknow Metro is a rapid transit system serving the city of Lucknow in Uttar Pradesh, India, designed to provide fast, modern urban transportation.
-
E.
Hyderabad Metro
Hyderabad Metro is a rapid transit system serving the city of Hyderabad, India, featuring multiple elevated corridors designed to ease urban traffic congestion and improve public transportation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4eafd348190986f69aee787fd8f |
completed | March 8, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4c3d0f2d88190b31e8c336f1a1bf3 |
completed | March 14, 2026, 2:11 a.m. |
Created at: March 8, 2026, 3:26 p.m.