Triple
T17430389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Meredith Victory |
E423852
|
entity |
| Predicate | associatedWithPort |
P2830
|
FINISHED |
| Object | Hungnam |
—
|
NE NERFINISHED |
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: Hungnam | Statement: [SS Meredith Victory, associatedWithPort, Hungnam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hungnam Context triple: [SS Meredith Victory, associatedWithPort, Hungnam]
-
A.
Hungnam
chosen
Hungnam is a port city on North Korea’s east coast that served as a major industrial center and the site of a large-scale UN evacuation during the Korean War.
-
B.
Phyongwon
Phyongwon is a city in North Korea known as an administrative and agricultural center within North Pyongan Province.
-
C.
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.
-
D.
Kŭmchŏng
Kŭmchŏng is a Korean place name element that appears in geographic designations such as the district name Kŭmchŏng-gu.
-
E.
Nampo
Nampo is a major port city in southwestern North Korea, known for its industrial facilities and strategic location on the Yellow Sea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448ffb9c8819099fabfeebdc06883 |
completed | April 19, 2026, 3:16 a.m. |
Created at: April 10, 2026, 5:46 a.m.