Triple
T3383504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trowulan |
E71241
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Jombang |
E227436
|
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: Jombang | Statement: [Trowulan, near, Jombang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jombang Context triple: [Trowulan, near, Jombang]
-
A.
Jombang
chosen
Jombang is a regency-level town in Indonesia known as an important regional center in the province of East Java.
-
B.
Lamongan
Lamongan is a regency and its capital town in the northern coastal region of East Java, Indonesia, known for its fishing industry and distinctive local cuisine.
-
C.
Nganjuk
Nganjuk is a regency capital and regional urban center in the province of East Java, Indonesia.
-
D.
Tulungagung
Tulungagung is a regency and urban center in southern East Java, Indonesia, known for its marble industry and coastal landscapes along the Indian Ocean.
-
E.
Probolinggo
Probolinggo is a coastal city in East Java, Indonesia, known as a common gateway for tourists visiting the Mount Bromo volcanic area.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5ec85d08190b28110157c39435f |
completed | March 8, 2026, 5:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5d035d97081908688d63527fd0f66 |
completed | March 14, 2026, 9:16 p.m. |
Created at: March 8, 2026, 3:14 p.m.