Triple
T24500773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gukje Sijang |
E617925
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object |
국제시장
국제시장은 부산 중구에 위치한 한국의 대표적인 재래시장으로, 다양한 상점과 먹거리, 생활용품을 판매하며 관광객과 현지인 모두에게 인기 있는 전통 시장이다.
|
E1638413
|
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: 국제시장 | Statement: [Gukje Sijang, hasAlternativeName, 국제시장]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 국제시장 Triple: [Gukje Sijang, hasAlternativeName, 국제시장]
Generated description
국제시장은 부산 중구에 위치한 한국의 대표적인 재래시장으로, 다양한 상점과 먹거리, 생활용품을 판매하며 관광객과 현지인 모두에게 인기 있는 전통 시장이다.
Provenance (5 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a800d9a88190b5970784a3f03ab8 |
completed | April 30, 2026, 12:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fee874cd081908bfdc0bb7dc4d02c |
completed | May 22, 2026, 5:49 a.m. |
| NEDg | Description generation | batch_6a0fefe9541481909d7dbd79fdf1ef92 |
completed | May 22, 2026, 5:55 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0ff0cecaf48190951f21afea7a103c |
completed | May 22, 2026, 5:59 a.m. |
Created at: April 18, 2026, 2:23 a.m.