Triple
T10028795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongbu Line |
E204798
|
entity |
| Predicate | passesThrough |
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: [Gyeongbu Line, passesThrough, Miryang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Miryang Context triple: [Gyeongbu Line, passesThrough, 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.
Myeong-bok
Myeong-bok is the given name of Gojong, the 26th king of the Joseon dynasty and first emperor of the Korean Empire.
-
C.
Nakchhong
Nakchhong is a traditional ritual specialist and religious officiant within the Kirat Mundhum indigenous belief system.
-
D.
Minyong
Minyong is a subgroup of the Adi people, an indigenous community of Arunachal Pradesh in Northeast India known for its distinct language and cultural traditions.
-
E.
Mokneung
Mokneung is one of the royal burial sites from Korea’s Joseon Dynasty, forming part of the UNESCO-listed Royal Tombs complex.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcde51c408190afb34010b1707014 |
completed | April 2, 2026, 2:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d282351ebc8190b22bf3964823b0ee |
completed | April 5, 2026, 3:39 p.m. |
Created at: March 30, 2026, 8:54 p.m.