Triple
T13739354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond Bridge |
E330038
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Yeongnam |
E740413
|
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: Yeongnam | Statement: [Diamond Bridge, region, Yeongnam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yeongnam Context triple: [Diamond Bridge, region, Yeongnam]
-
A.
Yeongnam
chosen
Yeongnam is a southeastern region of South Korea that includes major cities like Busan and Daegu and is known for its industrial centers and rich cultural heritage.
-
B.
Gyeongbuk
Gyeongbuk is a province in eastern South Korea known for its historical sites, cultural heritage, and scenic rural landscapes.
-
C.
Nakchhong
Nakchhong is a traditional ritual specialist and religious officiant within the Kirat Mundhum indigenous belief system.
-
D.
Yeoncheon
Yeoncheon is a county in Gyeonggi Province, South Korea, known for its location near the Demilitarized Zone (DMZ) and its significant historical and military sites.
-
E.
Myeong-bok
Myeong-bok is the given name of Gojong, the 26th king of the Joseon dynasty and first emperor of the Korean Empire.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0204d50c8190a5413cc9a1b26e14 |
completed | April 14, 2026, 8:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c6fe88348190aa9803f7d6d67023 |
completed | May 3, 2026, 10:06 p.m. |
Created at: April 9, 2026, 9:55 p.m.