Triple
T5565970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul Special City |
E145879
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | Gyeongseong |
E317908
|
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: Gyeongseong | Statement: [Seoul Special City, formerName, Gyeongseong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gyeongseong Context triple: [Seoul Special City, formerName, Gyeongseong]
-
A.
Gyeongseong
chosen
Gyeongseong was the Japanese colonial-era name for Seoul, which served as the administrative and political center of Korea under Japanese rule.
-
B.
Gwangalli
Gwangalli is a coastal neighborhood in Busan, South Korea, best known for its sandy beach, vibrant nightlife, and scenic views of the nearby Gwangan Bridge.
-
C.
Joseongeul
Joseongeul is the native Korean alphabetic writing system, more commonly known today as Hangul.
-
D.
Soi-myeon
Soi-myeon is a rural township-level administrative area located within Eumseong County in North Chungcheong Province, South Korea.
-
E.
Seogwipo
Seogwipo is a coastal city on South Korea’s Jeju Island known for its waterfalls, volcanic landscapes, and popular tourist attractions.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02034fc3081908920c52a19d462e1 |
completed | March 22, 2026, 5 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c059f006e081908c332f0470f38374 |
completed | March 22, 2026, 9:06 p.m. |
Created at: March 22, 2026, 3:36 p.m.