Triple
T5984779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XXIII Olympic Winter Games |
E133199
|
entity |
| Predicate | mascot |
P52
|
FINISHED |
| Object | Soohorang |
E145955
|
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: Soohorang | Statement: [XXIII Olympic Winter Games, mascot, Soohorang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Soohorang Context triple: [XXIII Olympic Winter Games, mascot, Soohorang]
-
A.
Soohorang
chosen
Soohorang is the white tiger character that served as the official mascot of the 2018 Winter Olympics in Pyeongchang, South Korea.
-
B.
Jinwicheon
Jinwicheon is a river flowing through the city of Pyeongtaek in South Korea.
-
C.
Sojin
Sojin is a given name, often used in East Asian cultures, that can refer to various individuals in entertainment, arts, and other fields.
-
D.
Seonghwan
Seonghwan is a locality in South Korea historically noted as the site of the Battle of Seonghwan during the First Sino-Japanese War.
-
E.
Hyeonreung
Hyeonreung is a royal tomb from Korea’s Joseon Dynasty, notable as one of the UNESCO-listed burial sites of its kings and queens.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04a6dcaf08190bac27c7042e65e07 |
completed | March 22, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e42a0fcc8190ab8d7f797b58a8e0 |
completed | March 23, 2026, 6:56 a.m. |
Created at: March 22, 2026, 4:04 p.m.