Triple
T30253000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 금정산 |
E769257
|
entity |
| Predicate | culturalProperty |
P122266
|
FINISHED |
| Object |
금정산성
금정산성은 부산 금정산 일대에 축조된 조선시대 산성으로, 왜구와 외침에 대비하기 위한 군사·방어 목적의 성곽 유적으로 잘 알려져 있다.
|
E1905860
|
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: [금정산, culturalProperty, 금정산성]
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: [금정산, culturalProperty, 금정산성]
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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6807d23cc819094279e32d55ea1b8 |
completed | May 2, 2026, 10:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2764576dc081909ed06914644d7b59 |
completed | June 9, 2026, 12:54 a.m. |
| NEDg | Description generation | batch_6a276576a8088190acca28b607d0fb41 |
completed | June 9, 2026, 12:59 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a2766aef0c08190ad736595abed58f3 |
completed | June 9, 2026, 1:04 a.m. |
Created at: April 29, 2026, 7:40 p.m.