Triple
T11061632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biliran |
E261520
|
entity |
| Predicate | hasVolcanicFeature |
P6356
|
FINISHED |
| Object | Mount Suiro |
E342590
|
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: Mount Suiro | Statement: [Biliran, hasVolcanicFeature, Mount Suiro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mount Suiro Context triple: [Biliran, hasVolcanicFeature, Mount Suiro]
-
A.
Mount Suiro
chosen
Mount Suiro is the tallest mountain on Biliran Island in the Philippines, forming a prominent part of the island’s volcanic landscape.
-
B.
Mount Sankaku
Mount Sankaku is a small, popular hiking and viewpoint mountain located in Nishi-ku, Sapporo, Japan.
-
C.
Mount Tsubakuro
Mount Tsubakuro is a popular alpine peak in Japan’s Northern Alps, known for its panoramic views, distinctive white granite ridges, and accessible hiking routes.
-
D.
Mount Goryu
Mount Goryu is a prominent peak in Japan’s Northern Alps, known for its ski resorts and alpine hiking within the Hakuba Valley area.
-
E.
Mount Tsurumi
Mount Tsurumi is a volcanic mountain in Ōita Prefecture, Japan, known for its panoramic views, seasonal foliage, and ropeway access from the hot spring resort city of Beppu.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798ea834c819099401e69f995c59f |
completed | April 9, 2026, 12:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f470cbce14819099d47d468ae61df7 |
completed | May 1, 2026, 9:22 a.m. |
Created at: April 8, 2026, 9:26 p.m.