Triple
T18549241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeju City |
E453323
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Jeju Port |
—
|
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: Jeju Port | Statement: [Jeju City, hasPort, Jeju Port]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jeju Port Context triple: [Jeju City, hasPort, Jeju Port]
-
A.
Jeju Port
chosen
Jeju Port is a major maritime gateway on South Korea’s Jeju Island, serving as a key hub for passenger ferries, cargo shipping, and regional 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.
Busan South Port
Busan South Port is a major harbor area in Busan, South Korea, serving as an important hub for maritime trade and transportation.
-
D.
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.
-
E.
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.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534beeb408190a03f6d7c3f2ef389 |
completed | April 19, 2026, 8:02 p.m. |
Created at: April 10, 2026, 11:38 a.m.