Triple
T7358647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Banten |
E169689
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Serang |
E122015
|
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: Serang | Statement: [Old Banten, near, Serang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Serang Context triple: [Old Banten, near, Serang]
-
A.
Serang
chosen
Serang is the capital city of Banten Province on the western tip of Java, Indonesia, serving as an important regional administrative and economic center.
-
B.
Cilegon
Cilegon is an industrial port city in western Java, Indonesia, known for its steel industry and strategic location near the Sunda Strait.
-
C.
Tangerang
Tangerang is a major urban and industrial city in Indonesia located just west of Jakarta on the island of Java.
-
D.
Parung
Parung is a district-level area in West Java, Indonesia, situated within the suburban region south of Jakarta and administered as part of Bogor Regency.
-
E.
Bandar Lampung
Bandar Lampung is a major port city in southern Sumatra, Indonesia, serving as the capital of Lampung Province and a key gateway between the island and Java.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f13db3488190ad35725c4fc60ffe |
completed | March 27, 2026, 9:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c802b69cb4819096815b1fac284840 |
completed | March 28, 2026, 4:32 p.m. |
Created at: March 27, 2026, 3:06 p.m.