Triple
T7978787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namhang Bridge |
E185512
|
entity |
| Predicate | locatedInWaterBody |
P1714
|
FINISHED |
| Object | Busan Harbor |
E704893
|
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: Busan Harbor | Statement: [Namhang Bridge, locatedInWaterBody, Busan Harbor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Busan Harbor Context triple: [Namhang Bridge, locatedInWaterBody, Busan Harbor]
-
A.
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.
-
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.
Incheon Port
Incheon Port is a major seaport in Incheon, South Korea, serving as a key gateway for international trade and maritime transport near the capital Seoul.
-
D.
Namhang Harbor
chosen
Namhang Harbor is a coastal port area known as a key maritime and industrial hub in Busan, South Korea.
-
E.
Jeju Port
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.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bf84b1081908e60a556d984aad6 |
completed | March 31, 2026, 3:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd33e50f0c81909c96da2d78f17ffd |
completed | April 1, 2026, 3:04 p.m. |
Created at: March 30, 2026, 5:14 p.m.