Triple
T14241511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwanak-gu |
E353016
|
entity |
| Predicate | hasNeighbour |
P5707
|
FINISHED |
| Object | Anyang-si |
E241609
|
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: Anyang-si | Statement: [Gwanak-gu, hasNeighbour, Anyang-si]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anyang-si Context triple: [Gwanak-gu, hasNeighbour, Anyang-si]
-
A.
Anyang
chosen
Anyang is a mid-sized South Korean city in the Seoul Capital Area known for its residential districts, light industry, and proximity to central Seoul.
-
B.
Anyang
Anyang is an ancient city in northern China renowned as one of the historical capitals of the Shang dynasty and a major archaeological site.
-
C.
Siheung
Siheung is a coastal city in northwestern South Korea known for its industrial complexes, wetlands, and proximity to Seoul.
-
D.
Namyangju
Namyangju is a city in South Korea known for its scenic natural landscapes, historical sites, and role as a suburban area within the Seoul metropolitan region.
-
E.
Pohang
Pohang is a major industrial and port city in South Korea, best known as the home of the global steelmaker POSCO and a key hub on the country’s east coast.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6244ad188190b9d9db7914240410 |
completed | April 14, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0cd12c308190ac868ffe7c5539b0 |
completed | May 8, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:08 a.m.