Triple
T21043024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rancaekek |
E518375
|
entity |
| Predicate | transportConnection |
P1298
|
FINISHED |
| Object | Bandung–Cirebon railway corridor |
—
|
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–Cirebon railway corridor | Statement: [Rancaekek, transportConnection, Bandung–Cirebon railway corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bandung–Cirebon railway corridor Context triple: [Rancaekek, transportConnection, Bandung–Cirebon railway corridor]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Jakarta–Bogor railway
The Jakarta–Bogor railway is a major commuter and intercity rail line in West Java, Indonesia, connecting the capital city Jakarta with the regional city of Bogor.
- 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–Cirebon railway corridor Target entity description: The Bandung–Cirebon railway corridor is a key rail line in West Java, Indonesia, linking the inland highland city of Bandung with the coastal city of Cirebon and serving numerous intermediate towns and commuter areas.
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Jakarta–Bogor railway
The Jakarta–Bogor railway is a major commuter and intercity rail line in West Java, Indonesia, connecting the capital city Jakarta with the regional city of Bogor.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf1950081908ff9fe8719e1e81b |
completed | April 21, 2026, 4:28 a.m. |
Created at: April 16, 2026, 2:17 p.m.