Triple
T6784117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 부산광역시 북구 |
E155757
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | 구포동 |
E617781
|
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: [부산광역시 북구, hasSubdivision, 구포동]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 구포동 Context triple: [부산광역시 북구, hasSubdivision, 구포동]
-
A.
구포동
chosen
구포동은 대한민국 부산광역시 북구에 위치한 행정동으로, 낙동강 인근에 자리한 주거 및 상업 지역이다.
-
B.
Deokpo-dong
Deokpo-dong is a neighborhood (dong) located within Sasang District in the city of Busan, South Korea.
-
C.
Sogyeok-dong
Sogyeok-dong is a neighborhood in central Seoul, South Korea, known for its traditional Korean houses (hanok), art galleries, and proximity to historic palaces.
-
D.
Sasang-dong
Sasang-dong is a neighborhood in Busan, South Korea, known as an urban residential and commercial area within the city's Sasang District.
-
E.
Gaepo-dong
Gaepo-dong is a residential neighborhood in Seoul, South Korea, known for its affluent housing, educational institutions, and location within the upscale Gangnam area.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d28bdc3c8190aa60616d89db66ed |
completed | March 27, 2026, 6:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71a84c0c48190be87bff2da4e69a1 |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:14 p.m.