Triple
T8187282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imjin River |
E191216
|
entity |
| Predicate | nearCity |
P350
|
FINISHED |
| Object | Paju |
E226748
|
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: Paju | Statement: [Imjin River, nearCity, Paju]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paju Context triple: [Imjin River, nearCity, Paju]
-
A.
Paju
chosen
Paju is a city in South Korea near the Demilitarized Zone, known for its historical sites, cultural complexes, and role as a border hub with North Korea.
-
B.
Balgüe
Balgüe is a small rural village on Ometepe Island in Lake Nicaragua, known for its scenic setting near volcanic landscapes and eco-tourism lodges.
-
C.
Soreang
Soreang is a suburban district and the administrative center of Bandung Regency in West Java, Indonesia, situated within the greater Bandung metropolitan area.
-
D.
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.
-
E.
Sokcho
Sokcho is a coastal city in northeastern South Korea known for its beaches, seafood, and proximity to Seoraksan National Park.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4d9e01208190842170abf62d9afb |
completed | March 31, 2026, 4:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd3489fd8c8190a919aff6e3b3df31 |
completed | April 1, 2026, 3:06 p.m. |
Created at: March 30, 2026, 5:41 p.m.