Triple
T5575214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jongno-gu |
E146300
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Cheonggyecheon |
E533618
|
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: Cheonggyecheon | Statement: [Jongno-gu, hasRiver, Cheonggyecheon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cheonggyecheon Context triple: [Jongno-gu, hasRiver, Cheonggyecheon]
-
A.
Cheonggyecheon Stream
chosen
Cheonggyecheon Stream is a restored urban waterway and public recreation space running through central Seoul, South Korea.
-
B.
Anseongcheon
Anseongcheon is a river in South Korea that flows through the city of Pyeongtaek in Gyeonggi Province.
-
C.
Hwanggujicheon
Hwanggujicheon is a stream in Osan, South Korea, that serves as a local waterway and natural feature of the city’s landscape.
-
D.
Jeongdong-gil
Jeongdong-gil is a historic street in central Seoul, South Korea, known for its scenic stone-wall road, cultural sites, and proximity to royal and governmental landmarks.
-
E.
Yudeungcheon
Yudeungcheon is a river in Daejeon, South Korea, known for flowing through the city’s urban areas and serving as a local recreational and ecological space.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02067e8d8819090a006cb266da5fe |
completed | March 22, 2026, 5:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04d1c6c008190978682491cca1e84 |
completed | March 22, 2026, 8:12 p.m. |
Created at: March 22, 2026, 3:37 p.m.