Triple
T19195957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noida Sector 137 |
E469967
|
entity |
| Predicate | servedByLine |
P1293
|
FINISHED |
| Object | Aqua Line |
—
|
NE NERFINISHED |
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: Aqua Line | Statement: [Noida Sector 137, servedByLine, Aqua Line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aqua Line Context triple: [Noida Sector 137, servedByLine, Aqua Line]
-
A.
Aqua Line
Aqua Line is one of the main corridors of the Nagpur Metro rapid transit system in Nagpur, India.
-
B.
Aqua Line
chosen
Aqua Line is a rapid transit corridor of the Noida Metro system serving key areas of Noida and Greater Noida in the Delhi National Capital Region.
-
C.
Harbour Line
Harbour Line is a major corridor of Mumbai's suburban railway network that connects the city’s eastern waterfront and Navi Mumbai suburbs to key central and southern Mumbai terminals.
-
D.
Harbour Line
Harbour Line is a Copenhagen Metro route that serves areas along the city’s waterfront and harbor districts.
-
E.
W Line
The W Line is a light rail route in the Denver metropolitan area that connects downtown Denver with the western suburbs as part of the Regional Transportation District (RTD) system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a5dabc81908fffad811f177b03 |
completed | April 20, 2026, 9:57 a.m. |
Created at: April 10, 2026, 12:07 p.m.