Triple
T18117822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Sinabung |
E433654
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Lake Toba region |
—
|
NE NERFINISHED |
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: Lake Toba region | Statement: [Mount Sinabung, locatedNear, Lake Toba region]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lake Toba region Context triple: [Mount Sinabung, locatedNear, Lake Toba region]
-
A.
Toba Highlands
chosen
Toba Highlands is a volcanic highland region in North Sumatra, Indonesia, known for its dramatic landscapes surrounding Lake Toba and its rich Batak cultural heritage.
-
B.
Toba Kakar area
The Toba Kakar area is a mountainous region in western Pakistan’s Balochistan province, forming part of the Toba Kakar Range near the Afghan border.
-
C.
Toba Batak
Toba Batak is an Austronesian language spoken primarily by the Toba Batak people of North Sumatra, Indonesia.
-
D.
Toba
Toba is a coastal city in central Japan’s Mie Prefecture, known for its pearl cultivation, scenic bays, and maritime heritage.
-
E.
Toba
Toba was a 12th-century Japanese emperor of the late Heian period whose reign and later cloistered rule significantly influenced imperial politics.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd737708190863fba97cdc20d88 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 10:28 a.m.