Triple
T1709327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean Empire |
E36940
|
entity |
| Predicate | flag |
P401
|
FINISHED |
| Object | Taegukgi |
E25691
|
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: Taegukgi | Statement: [Korean Empire, flag, Taegukgi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taegukgi Context triple: [Korean Empire, flag, Taegukgi]
-
A.
Gwangandaegyo
Gwangandaegyo is a prominent suspension bridge in Busan, South Korea, known for its scenic coastal views and nighttime LED light displays.
-
B.
Aegukga
chosen
Aegukga is the national anthem of South Korea, expressing patriotic devotion and love for the country.
-
C.
Jagalchi Sijang
Jagalchi Sijang is South Korea’s largest and most famous seafood market, located along the waterfront in Busan and renowned for its vast array of fresh and live seafood.
-
D.
Hanguk Suhwagi
Hanguk Suhwagi is the Korean Sign Language used by the Deaf community in South Korea for everyday communication and cultural expression.
-
E.
Seoul Special City
Seoul Special City is the capital and largest metropolis of South Korea, serving as the country’s political, economic, and cultural center.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa631329088190a2ce8f755bd69fc7 |
completed | March 6, 2026, 5:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad8adb1b588190b93f9d28d27cab72 |
completed | March 8, 2026, 2:42 p.m. |
Created at: March 4, 2026, 7:30 p.m.