Triple
T18526267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BD |
E452724
|
entity |
| Predicate | associatedRailwayLine |
P848
|
FINISHED |
| Object | Bandung–Surabaya route |
—
|
NE NERFINISHED |
How this triple was built (3 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: Bandung–Surabaya route | Statement: [BD, associatedRailwayLine, Bandung–Surabaya route]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bandung–Surabaya route Context triple: [BD, associatedRailwayLine, Bandung–Surabaya route]
-
A.
Jakarta–Surabaya corridor
The Jakarta–Surabaya corridor is Indonesia’s principal rail artery on Java, linking the capital with its second-largest city and serving as a key backbone for passenger and freight transport.
-
B.
Bandung–Garut railway
The Bandung–Garut railway is a rail line in West Java, Indonesia, that historically connected the city of Bandung with the town of Garut, serving as an important regional transport route.
-
C.
Jakarta–Bandung railway
The Jakarta–Bandung railway is a major rail corridor in Indonesia that connects the capital city Jakarta with the highland city of Bandung, serving as a key route for passenger and regional transport across West Java.
-
D.
Bandung–Cicalengka railway
The Bandung–Cicalengka railway is a key commuter and regional rail line in West Java, Indonesia, connecting the city of Bandung with the eastern town of Cicalengka as part of the broader Bandung metropolitan rail network.
-
E.
Bandung–Banjar railway
The Bandung–Banjar railway is a rail line in West Java, Indonesia, connecting the inland city of Bandung with the town of Banjar and forming part of the region’s intercity rail network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Bandung–Surabaya route Target entity description: The Bandung–Surabaya route is a major intercity rail corridor in Indonesia connecting the city of Bandung in West Java with Surabaya in East Java.
-
A.
Jakarta–Surabaya corridor
The Jakarta–Surabaya corridor is Indonesia’s principal rail artery on Java, linking the capital with its second-largest city and serving as a key backbone for passenger and freight transport.
-
B.
Bandung–Garut railway
The Bandung–Garut railway is a rail line in West Java, Indonesia, that historically connected the city of Bandung with the town of Garut, serving as an important regional transport route.
-
C.
Jakarta–Bandung railway
The Jakarta–Bandung railway is a major rail corridor in Indonesia that connects the capital city Jakarta with the highland city of Bandung, serving as a key route for passenger and regional transport across West Java.
-
D.
Bandung–Cicalengka railway
The Bandung–Cicalengka railway is a key commuter and regional rail line in West Java, Indonesia, connecting the city of Bandung with the eastern town of Cicalengka as part of the broader Bandung metropolitan rail network.
-
E.
Bandung–Banjar railway
The Bandung–Banjar railway is a rail line in West Java, Indonesia, connecting the inland city of Bandung with the town of Banjar and forming part of the region’s intercity rail network.
- F. None of above. chosen
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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53392618c8190b44de46b80ee6a6d |
completed | April 19, 2026, 7:57 p.m. |
Created at: April 10, 2026, 11:37 a.m.