Triple
T26335967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chongchon River |
E662520
|
entity |
| Predicate | hasNameInKorean |
P17869
|
FINISHED |
| Object |
청천강
청천강은 북한 서부를 흐르며 황해로 유입되는 주요 하천으로, 주변 지역의 농업과 산업에 중요한 역할을 하는 강이다.
|
E1828937
|
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: [Chongchon River, hasNameInKorean, 청천강]
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: [Chongchon River, hasNameInKorean, 청천강]
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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f6cf3208190816114685e00e96c |
completed | May 2, 2026, 2:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1cc34da4ac8190a252d8f935c07e65 |
completed | May 31, 2026, 11:25 p.m. |
| NEDg | Description generation | batch_6a1cc42a1b08819092125b1f3d09f2ca |
completed | May 31, 2026, 11:28 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a1cc4e253288190bb4e761d17423cbf |
completed | May 31, 2026, 11:31 p.m. |
Created at: April 26, 2026, 10:36 p.m.