Triple
T28350196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 임진강 |
E718071
|
entity |
| Predicate | hasFacility |
P105
|
FINISHED |
| Object |
임진각 평화누리
임진각 평화누리는 비무장지대 인근 파주에 조성된 대규모 평화·통일 테마 공원으로, 전쟁과 분단의 상징 공간을 문화예술과 휴식의 장으로 재구성한 관광지이다.
|
E1814712
|
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: [임진강, hasFacility, 임진각 평화누리]
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: [임진강, hasFacility, 임진각 평화누리]
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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c09bb108190844fb88c3cc8ebcf |
completed | May 2, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1627c4b96c81908d274af7d0e498eb |
completed | May 26, 2026, 11:07 p.m. |
| NEDg | Description generation | batch_6a1629f6f6b88190a44ee5f508e290ab |
completed | May 26, 2026, 11:17 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a162a882d7881908b4c7089a5d8bee9 |
completed | May 26, 2026, 11:19 p.m. |
Created at: April 28, 2026, 12:45 a.m.