Triple
T22852767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Coast of South Korea |
E566395
|
entity |
| Predicate | hasAttraction |
P105
|
FINISHED |
| Object | Jeongdongjin |
—
|
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: Jeongdongjin | Statement: [East Coast of South Korea, hasAttraction, Jeongdongjin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jeongdongjin Context triple: [East Coast of South Korea, hasAttraction, Jeongdongjin]
-
A.
Jeongdongjin
chosen
Jeongdongjin is a coastal town in South Korea famed for its scenic East Sea sunrise views and seaside railway station.
-
B.
Jinwicheon
Jinwicheon is a river flowing through the city of Pyeongtaek in South Korea.
-
C.
Seonghwa
Seonghwa was the era name used during the reign of King Seongjong of the Joseon dynasty in Korea, marking a specific period of his rule.
-
D.
Uicheon
Uicheon was an influential Korean Buddhist monk and scholar of the Goryeo dynasty, known for promoting the Cheontae (Tiantai) school and attempting to harmonize doctrinal and meditative traditions.
-
E.
Seonghwan
Seonghwan is a locality in South Korea historically noted as the site of the Battle of Seonghwan during the First Sino-Japanese War.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eba65a881908c484262c3ee5212 |
completed | April 29, 2026, 3:44 a.m. |
Created at: April 17, 2026, 3:36 p.m.