Triple
T20792277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salatiga |
E511806
|
entity |
| Predicate | hasMajorRoad |
P385
|
FINISHED |
| Object | Semarang–Solo 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: Semarang–Solo corridor | Statement: [Salatiga, hasMajorRoad, Semarang–Solo corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Semarang–Solo corridor Context triple: [Salatiga, hasMajorRoad, Semarang–Solo corridor]
-
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.
Yogyakarta–Solo main road
The Yogyakarta–Solo main road is a major arterial highway in Central Java, Indonesia, connecting the cities of Yogyakarta and Surakarta (Solo) and serving as a key corridor for regional travel and commerce.
-
C.
Jakarta–Merak corridor
The Jakarta–Merak corridor is a major transportation axis in western Java, Indonesia, linking the capital region around Jakarta with the key ferry port of Merak that connects Java to Sumatra.
-
D.
Palembang–Lampung corridor
The Palembang–Lampung corridor is a major railway route in southern Sumatra that links the cities of Palembang and Bandar Lampung, serving as a key axis for passenger and freight transport in Indonesia.
-
E.
Yogyakarta–Solo railway line
The Yogyakarta–Solo railway line is a key rail corridor in Central Java, Indonesia, connecting the major cultural and economic centers of Yogyakarta and Surakarta (Solo) and serving numerous intermediate towns and regencies.
- 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: Semarang–Solo corridor Target entity description: The Semarang–Solo corridor is a key transportation route in Central Java, Indonesia, linking the major cities of Semarang and Surakarta (Solo) and serving as an important axis for regional travel and commerce.
-
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.
Yogyakarta–Solo main road
The Yogyakarta–Solo main road is a major arterial highway in Central Java, Indonesia, connecting the cities of Yogyakarta and Surakarta (Solo) and serving as a key corridor for regional travel and commerce.
-
C.
Jakarta–Merak corridor
The Jakarta–Merak corridor is a major transportation axis in western Java, Indonesia, linking the capital region around Jakarta with the key ferry port of Merak that connects Java to Sumatra.
-
D.
Palembang–Lampung corridor
The Palembang–Lampung corridor is a major railway route in southern Sumatra that links the cities of Palembang and Bandar Lampung, serving as a key axis for passenger and freight transport in Indonesia.
-
E.
Yogyakarta–Solo railway line
The Yogyakarta–Solo railway line is a key rail corridor in Central Java, Indonesia, connecting the major cultural and economic centers of Yogyakarta and Surakarta (Solo) and serving numerous intermediate towns and regencies.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2910d488190bc4be37512effc86 |
completed | April 21, 2026, 12:19 a.m. |
Created at: April 16, 2026, 12:38 p.m.