Triple
T6570312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeonsu District |
E155416
|
entity |
| Predicate | hasNeighborhood |
P40
|
FINISHED |
| Object | Songdo 3-dong |
E637403
|
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: Songdo 3-dong | Statement: [Yeonsu District, hasNeighborhood, Songdo 3-dong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Songdo 3-dong Context triple: [Yeonsu District, hasNeighborhood, Songdo 3-dong]
-
A.
Songdo-dong
chosen
Songdo-dong is a modern waterfront neighborhood in Incheon, South Korea, best known for hosting the high-tech, master-planned Songdo International Business District.
-
B.
Samseong-dong
Samseong-dong is a prominent neighborhood in Seoul, South Korea, known for its upscale shopping, business centers, and major landmarks like COEX Mall.
-
C.
Seongho-dong
Seongho-dong is a neighborhood (dong) within the city of Osan in Gyeonggi Province, South Korea.
-
D.
Samcheong-dong
Samcheong-dong is a picturesque neighborhood in central Seoul known for its traditional hanok houses, art galleries, cafes, and proximity to historic palaces.
-
E.
Okryeon-dong
Okryeon-dong is a neighborhood located within Yeonsu District in Incheon, 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_69c688151254819080387f87deab8fa7 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ae5791e881909d0b340aa63c6223 |
completed | March 27, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7b89caf148190a2959698e5849e12 |
completed | March 28, 2026, 11:16 a.m. |
Created at: March 27, 2026, 1:53 p.m.