Triple
T6804366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sampang Regency |
E156264
|
entity |
| Predicate | administrativeCenter |
P1474
|
FINISHED |
| Object | Sampang |
E143295
|
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: Sampang | Statement: [Sampang Regency, administrativeCenter, Sampang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sampang Context triple: [Sampang Regency, administrativeCenter, Sampang]
-
A.
Sampang
chosen
Sampang is a coastal city and regency capital on Madura Island in East Java, Indonesia, known for its traditional Madurese culture and agriculture-based economy.
-
B.
Tumpang
Tumpang is a subdistrict in Malang Regency, East Java, Indonesia, known for its proximity to historical temples and as a gateway to the Bromo-Tengger-Semeru area.
-
C.
Sasamungga
Sasamungga is a coastal village and local community on Choiseul Island in the Solomon Islands.
-
D.
Pakualaman
Pakualaman is a small hereditary Javanese princely state and court within Yogyakarta, established in the 19th century as a minor parallel to the main sultanate.
-
E.
Ngamprah
Ngamprah is an administrative town in West Java, Indonesia, serving as the governmental and economic center of West Bandung Regency.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2ea459c819095388218d53c250a |
completed | March 27, 2026, 6:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c723d525bc8190aaf2390d690dc6a6 |
completed | March 28, 2026, 12:41 a.m. |
Created at: March 27, 2026, 2:16 p.m.