Triple
T27621121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 국립해양박물관 |
E700580
|
entity |
| Predicate | locatedInTheAdministrativeTerritorialEntity |
P40
|
FINISHED |
| Object |
영도구
영도구는 부산광역시 남동부에 위치한 섬과 반도 지형으로 이루어진 해양·항만 산업과 관광이 발달한 자치구이다.
|
E1779455
|
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: [국립해양박물관, locatedInTheAdministrativeTerritorialEntity, 영도구]
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: [국립해양박물관, locatedInTheAdministrativeTerritorialEntity, 영도구]
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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f630dc90708190a1f81c7fb6562a75 |
completed | May 2, 2026, 5:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12d0f3755c81909a7f2a44140676ff |
completed | May 24, 2026, 10:20 a.m. |
| NEDg | Description generation | batch_6a12d16a912881909edf8e2359b34503 |
completed | May 24, 2026, 10:22 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a12d21a403881908ba269eefc7c160b |
completed | May 24, 2026, 10:25 a.m. |
Created at: April 27, 2026, 2:14 p.m.