Triple
T7719364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunsan |
E174966
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Iksan |
E649176
|
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: Iksan | Statement: [Gunsan, borders, Iksan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iksan Context triple: [Gunsan, borders, Iksan]
-
A.
Iksan
chosen
Iksan is a city in South Korea’s North Jeolla Province known as a key transportation hub and historical center with significant Baekje-era cultural heritage.
-
B.
Ishkashimi
Ishkashimi is a lesser-known Eastern Iranian language spoken by small communities in parts of Afghanistan and Tajikistan.
-
C.
Kariya
Kariya is a Japanese surname most notably associated with former NHL star Paul Kariya.
-
D.
Dairen
Dairen, now known as Dalian, is a major port city in northeastern China that historically served as an important strategic and commercial hub under various foreign leases and administrations.
-
E.
Tenjin
Tenjin is the Shinto kami of scholarship and learning, widely revered by students seeking academic success.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702eedc088190be645c029dfc462a |
completed | March 27, 2026, 10:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8b513f7d481908d2ce64d9685289c |
completed | March 29, 2026, 5:13 a.m. |
Created at: March 27, 2026, 4:05 p.m.