Triple
T16535420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suwon |
E401676
|
entity |
| Predicate | hasCuisineSpecialty |
P5786
|
FINISHED |
| Object | Suwon galbi |
E489924
|
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: Suwon galbi | Statement: [Suwon, hasCuisineSpecialty, Suwon galbi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Suwon galbi Context triple: [Suwon, hasCuisineSpecialty, Suwon galbi]
-
A.
Ankwei-Goemai
Ankwei-Goemai is an alternative name for the Goemai language spoken by the Goemai people of central Nigeria.
-
B.
Bulgogi
chosen
Bulgogi is a popular Korean dish of thinly sliced, marinated beef grilled or pan-cooked for a savory-sweet flavor.
-
C.
Baeggu
Baeggu is an Oceanic language of the Meso-Melanesian group spoken by a small community in the Solomon Islands.
-
D.
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.
-
E.
Gukje Sijang
Gukje Sijang is one of South Korea’s largest and most famous traditional markets, located in Busan and known for its wide variety of goods and bustling atmosphere.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e345574d88819094548367bf983078 |
completed | April 18, 2026, 8:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006094dee481908757b84c10d0dc19 |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 5:15 a.m.