Triple
T12057592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 손기정 |
E287081
|
entity |
| Predicate | placeOfBirth |
P1
|
FINISHED |
| Object | 대한제국 경성부 |
E584189
|
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: [손기정, placeOfBirth, 대한제국 경성부]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 대한제국 경성부 Context triple: [손기정, placeOfBirth, 대한제국 경성부]
-
A.
Sejong City
Sejong City is South Korea’s planned administrative capital, designed to house numerous government ministries and ease congestion in Seoul.
-
B.
Keijō
chosen
Keijō was the Japanese colonial name for Seoul, which served as the administrative center of Japanese-ruled Korea.
-
C.
Kangbuk-gu, Seoul
Kangbuk-gu, Seoul is a northern district of South Korea’s capital city known for its residential neighborhoods, mountainous landscapes, and cultural sites.
-
D.
Jinju-si
Jinju-si is a city in South Gyeongsang Province, South Korea, known for its historic Jinju Fortress and the annual Namgang Yudeung (Lantern) Festival.
-
E.
Hanseong
Hanseong was the historical name for Seoul when it served as the capital of the Joseon Dynasty in Korea.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9043bf0ec8190a51ef2641808320c |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f49dea043c8190a74ffb448bbae5d0 |
completed | May 1, 2026, 12:34 p.m. |
Created at: April 8, 2026, 9:47 p.m.