Triple
T6248136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Courts of South Korea |
E139772
|
entity |
| Predicate | hasSeatIn |
P3522
|
FINISHED |
| Object | Ulsan |
E28895
|
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: Ulsan | Statement: [District Courts of South Korea, hasSeatIn, Ulsan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulsan Context triple: [District Courts of South Korea, hasSeatIn, Ulsan]
-
A.
Ulsan
chosen
Ulsan is a major industrial city in southeastern South Korea, known for its large automobile, shipbuilding, and petrochemical complexes.
-
B.
Pohang
Pohang is a major industrial and port city in South Korea, best known as the home of the global steelmaker POSCO and a key hub on the country’s east coast.
-
C.
Daegu
Daegu is a major metropolitan city in southeastern South Korea known for its textile industry, electronics manufacturing, and cultural festivals.
-
D.
Gunsan
Gunsan is a coastal city in North Jeolla Province, South Korea, known for its port, industrial facilities, and longstanding association with nearby military air operations.
-
E.
Busan
Busan is South Korea’s second-largest city and a major international port known for its bustling harbor, beaches, and coastal scenery.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0633a9a048190856d5247d3b28a2e |
completed | March 22, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6caf09b408190b1133afa52668bfe |
completed | March 27, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:23 p.m.