Triple
T23485874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 안익태 편곡 선율 |
E570530
|
entity |
| Predicate | 저작권 관련 논의 |
P57127
|
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.
containsDiscussionOf
Indicates that one entity includes or features a discussion, treatment, or consideration of another entity as a topic or subject.
-
B.
debatedWithin
chosen
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
C.
frequentlyDiscussedIn
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
D.
influencedDiscussionOf
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
-
E.
discussed
Indicates that one entity talked about, examined, or debated a topic, issue, or other entity with someone else.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7538a8c8190b7effcc39a3f9787 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:03 p.m.