Triple
T5565992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul Special City |
E145879
|
entity |
| Predicate | hasBusinessDistrict |
P459
|
FINISHED |
| Object | Jongno |
E350135
|
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: Jongno | Statement: [Seoul Special City, hasBusinessDistrict, Jongno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jongno Context triple: [Seoul Special City, hasBusinessDistrict, Jongno]
-
A.
Cheongdam-dong
Cheongdam-dong is an affluent neighborhood in Seoul known for its luxury boutiques, high-end residences, and trendy cafes and galleries.
-
B.
Jongno District
chosen
Jongno District is a central historic and administrative area of Seoul, South Korea, known for its government institutions, cultural landmarks, and traditional neighborhoods.
-
C.
Yeouido-dong
Yeouido-dong is a major financial and business district in Seoul, South Korea, known for its skyscrapers, corporate headquarters, and role as a political and economic hub.
-
D.
Yangjeong-dong
Yangjeong-dong is a neighborhood (dong) located within Busanjin District in the city of Busan, South Korea.
-
E.
Cheongnyong-dong
Cheongnyong-dong is a neighborhood located within Geumjeong District in Busan, South 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_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_69c097bd26e08190a687a08323f1400a |
completed | March 23, 2026, 1:30 a.m. |
Created at: March 22, 2026, 3:36 p.m.