Triple
T5507088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakdong River |
E144467
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Miryang |
E162206
|
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: Miryang | Statement: [Nakdong River, flowsThrough, Miryang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Miryang Context triple: [Nakdong River, flowsThrough, Miryang]
-
A.
Miryang
chosen
Miryang is a city in South Gyeongsang Province, South Korea, known for its scenic river valley setting, historical sites, and role as a regional transport and educational hub.
-
B.
Mokneung
Mokneung is one of the royal burial sites from Korea’s Joseon Dynasty, forming part of the UNESCO-listed Royal Tombs complex.
-
C.
Taebong
Taebong was a short-lived Korean kingdom of the early 10th century that emerged during the Later Three Kingdoms period before being absorbed by Goryeo.
-
D.
Seogwipo
Seogwipo is a coastal city on South Korea’s Jeju Island known for its waterfalls, volcanic landscapes, and popular tourist attractions.
-
E.
Ungjin
Ungjin was an ancient city in the Korean kingdom of Baekje that served as one of its historical capitals and a key political and cultural center.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f495c588190b0cfe5bfb3d2c221 |
completed | March 22, 2026, 4:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c027bc39208190baa01feadb75d3c6 |
completed | March 22, 2026, 5:32 p.m. |
Created at: March 22, 2026, 3:32 p.m.