Triple
T13112519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hwaseong |
E311006
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object |
Maesong Port
Maesong Port is a coastal port facility located in Hwaseong, South Korea, serving regional maritime transport and local fishing activities.
|
E1023800
|
NE FINISHED |
How this triple was built (4 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: Maesong Port | Statement: [Hwaseong, hasPort, Maesong Port]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maesong Port Context triple: [Hwaseong, hasPort, Maesong Port]
-
A.
Jeongok Port
Jeongok Port is a coastal harbor and marina located in Hwaseong, South Korea, serving as a regional hub for fishing, leisure boating, and marine tourism.
-
B.
Gunsan Port
Gunsan Port is a major seaport in Gunsan, South Korea, serving as an important hub for regional trade and maritime transport.
-
C.
Jangsaengpo Port
Jangsaengpo Port is a coastal port area in Ulsan, South Korea, historically known for its whaling industry and now a hub for marine tourism.
-
D.
Pyeongtaek Port
Pyeongtaek Port is a major South Korean seaport on the Yellow Sea that serves as an important hub for international trade and regional maritime logistics.
-
E.
Busan North Port
Busan North Port is a major harbor area in Busan, South Korea, serving as one of the city’s key maritime and logistics hubs.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Maesong Port Triple: [Hwaseong, hasPort, Maesong Port]
Generated description
Maesong Port is a coastal port facility located in Hwaseong, South Korea, serving regional maritime transport and local fishing activities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Maesong Port Target entity description: Maesong Port is a coastal port facility located in Hwaseong, South Korea, serving regional maritime transport and local fishing activities.
-
A.
Jeongok Port
Jeongok Port is a coastal harbor and marina located in Hwaseong, South Korea, serving as a regional hub for fishing, leisure boating, and marine tourism.
-
B.
Gunsan Port
Gunsan Port is a major seaport in Gunsan, South Korea, serving as an important hub for regional trade and maritime transport.
-
C.
Jangsaengpo Port
Jangsaengpo Port is a coastal port area in Ulsan, South Korea, historically known for its whaling industry and now a hub for marine tourism.
-
D.
Pyeongtaek Port
Pyeongtaek Port is a major South Korean seaport on the Yellow Sea that serves as an important hub for international trade and regional maritime logistics.
-
E.
Busan North Port
Busan North Port is a major harbor area in Busan, South Korea, serving as one of the city’s key maritime and logistics hubs.
- F. None of above. chosen
Provenance (5 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817f8ee8819084078b4bec5e4f18 |
completed | April 10, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6eadad81c8190881e6577e1c2a207 |
completed | May 3, 2026, 6:27 a.m. |
| NEDg | Description generation | batch_69f6ec35b5cc8190a84f522b7808324e |
completed | May 3, 2026, 6:33 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69f6ecaf2ed88190b973549bbb3d21ce |
completed | May 3, 2026, 6:35 a.m. |
Created at: April 9, 2026, 9:05 p.m.