Triple
T11041078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geumwang-eup |
E261016
|
entity |
| Predicate | locatedInRegion |
P40
|
FINISHED |
| Object | Hoseo |
E882463
|
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: Hoseo | Statement: [Geumwang-eup, locatedInRegion, Hoseo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hoseo Context triple: [Geumwang-eup, locatedInRegion, Hoseo]
-
A.
Hoseo
chosen
Hoseo is a historical region in central-western South Korea, encompassing parts of present-day Chungcheong provinces and known for its cultural and administrative significance.
-
B.
Man-il
Man-il is a Korean masculine given name that can be used by various individuals, including the person named Gim Man-il.
-
C.
Shaul
Shaul is the Hebrew form of the name Saul, most famously associated with the first king of ancient Israel in the Hebrew Bible.
-
D.
Jumong
Jumong is the legendary founder and first king of the ancient Korean kingdom of Goguryeo, celebrated as a heroic archer and culture hero in Korean history and mythology.
-
E.
King Sinmun
King Sinmun was a monarch of the Korean kingdom of Silla who played a key role in consolidating and governing the peninsula after its unification in the late 7th century.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7980050948190ae7b187da5b776ca |
completed | April 9, 2026, 12:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3a9e525508190bf3a728683eeec79 |
completed | April 18, 2026, 3:57 p.m. |
Created at: April 8, 2026, 9:26 p.m.