Triple
T19410791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fortress |
E485579
|
entity |
| Predicate | titleInKorean |
P60748
|
FINISHED |
| Object | 남한산성 |
—
|
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: 남한산성 | Statement: [The Fortress, titleInKorean, 남한산성]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 남한산성 Context triple: [The Fortress, titleInKorean, 남한산성]
-
A.
남한산성
chosen
남한산성은 병자호란 당시 조선 인조가 청나라에 맞서 항전하던 시기를 그린 황동혁 감독의 역사 영화이다.
-
B.
Achasanseong Fortress
Achasanseong Fortress is an ancient mountain stronghold in present-day Guri, South Korea, historically used as a strategic defensive site overlooking the Han River.
-
C.
Hwaseong Fortress
Hwaseong Fortress is a late 18th-century Korean fortification in Suwon renowned for its innovative military architecture and recognized as a UNESCO World Heritage Site.
-
D.
Jinjuseong Fortress
Jinjuseong Fortress is a historic riverside fortification in Jinju, South Korea, renowned for its role in the Imjin War and its well-preserved walls, gates, and cultural relics.
-
E.
Wanggeom-seong
Wanggeom-seong was the principal royal city and political center of the ancient Korean kingdom of Gojoseon, traditionally regarded as Korea’s first capital.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af4cc0c81909056b5e2ee574ab1 |
completed | April 20, 2026, 1:32 p.m. |
Created at: April 10, 2026, 1:37 p.m.