Triple
T27847012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 윤여정 |
E703851
|
entity |
| Predicate | 대표작 |
P4
|
FINISHED |
| Object |
완벽한 타인(한국 영화)
완벽한 타인(한국 영화)은 저녁 식사 자리에서 휴대전화 메시지를 모두 공개하기로 한 친구들의 게임을 통해 인간관계의 민낯과 비밀을 드러내는 블랙 코미디 드라마 영화이다.
|
E1792716
|
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: [윤여정, 대표작, 완벽한 타인(한국 영화)]
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: [윤여정, 대표작, 완벽한 타인(한국 영화)]
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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63902060081909bb490327b0c16f2 |
completed | May 2, 2026, 5:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12f73989c881909284c77eec14d780 |
completed | May 24, 2026, 1:03 p.m. |
| NEDg | Description generation | batch_6a12fb4a4a808190bc0821b2bc754da0 |
completed | May 24, 2026, 1:21 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a12fd21fb2c8190b52459bd901c05a0 |
completed | May 24, 2026, 1:29 p.m. |
Created at: April 27, 2026, 6:08 p.m.