Triple
T889553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul |
E19209
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 서울특별시 |
E19209
|
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: 서울특별시 | Statement: [Seoul, nativeName, 서울특별시]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 서울특별시 Context triple: [Seoul, nativeName, 서울특별시]
-
A.
Seoul
chosen
Seoul is the capital and largest metropolis of South Korea, known as a major global center for technology, culture, and finance.
-
B.
Incheon
Incheon is a major port city in northwestern South Korea, known for its international airport and role as a key transportation and economic hub.
-
C.
Gyeonggi Province
Gyeonggi Province is a populous region in northwestern South Korea that surrounds Seoul and serves as a key political, economic, and military hub of the country.
-
D.
Daejeon
Daejeon is a major city in central South Korea known as a hub for science, technology, and research institutions.
-
E.
Daegu
Daegu is a major metropolitan city in southeastern South Korea known for its textile industry, electronics manufacturing, and cultural festivals.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acff52008190ac2975c08ad29f54 |
completed | March 1, 2026, 9:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7c023464481909759c457e87266ab |
completed | March 4, 2026, 5:16 a.m. |
Created at: March 1, 2026, 7:39 p.m.