Triple
T22047809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seochon |
E544806
|
entity |
| Predicate | hasViewOf |
P854
|
FINISHED |
| Object | Inwangsan Mountain |
—
|
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: Inwangsan Mountain | Statement: [Seochon, hasViewOf, Inwangsan Mountain]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Inwangsan Mountain Context triple: [Seochon, hasViewOf, Inwangsan Mountain]
-
A.
Hwangnyeongsan Mountain
Hwangnyeongsan Mountain is a prominent peak in Busan, South Korea, known for its panoramic city and coastal views, especially popular at night.
-
B.
Eungbong Mountain
Eungbong Mountain is a small but popular urban peak in eastern Seoul, South Korea, known for its scenic views of the Han River and the city skyline.
-
C.
Umyeonsan Mountain
Umyeonsan Mountain is a low, forested peak in southern Seoul, South Korea, known for its hiking trails, city views, and role as a natural green space within the urban area.
-
D.
인왕산
chosen
인왕산은 서울 종로구에 위치한 바위산으로, 도심 속에서 한양도성과 서울 전경을 조망할 수 있는 대표적인 명산이다.
-
E.
Gwanggyo Mountain
Gwanggyo Mountain is a prominent natural landmark in South Korea known for its hiking trails and scenic views near the city of Suwon.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12830c674819080254d77ee02bc9f |
completed | April 28, 2026, 9:35 p.m. |
Created at: April 16, 2026, 8:26 p.m.