Triple
T19410650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 황동혁 |
E485576
|
entity |
| Predicate | 각본집필 |
P25235
|
FINISHED |
| Object | 도가니 각본 |
—
|
LITERAL 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: [황동혁, 각본집필, 도가니 각본]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 각본집필 Context triple: [황동혁, 각본집필, 도가니 각본]
-
A.
screenwriterOfWork
chosen
Indicates that a person served as the screenwriter (wrote the screenplay) for a particular creative work.
-
B.
screenplayBy
Indicates that a film, television show, or similar work was written or scripted by a particular person or group.
-
C.
screenplayWrittenFor
Indicates that a screenplay was written specifically for a particular film, show, or production.
-
D.
screenwriterOfWorkFeaturing
Indicates that one entity is the screenwriter responsible for creating the screenplay for a work in which the other entity appears or is featured.
-
E.
librettoBasedOn
Indicates that the libretto of a musical or operatic work is derived from, adapted from, or otherwise based on another pre-existing work or source.
- F. None of above.
Provenance (3 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af4cc0c81909056b5e2ee574ab1 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.