Triple
T27754021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 김대중 |
E701289
|
entity |
| Predicate | 피해경험 |
P2854
|
FINISHED |
| Object | 납치 사건(1973년 도쿄 김대중 납치 사건) |
—
|
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: 납치 사건(1973년 도쿄 김대중 납치 사건) | Statement: [김대중, 피해경험, 납치 사건(1973년 도쿄 김대중 납치 사건)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 피해경험 Context triple: [김대중, 피해경험, 납치 사건(1973년 도쿄 김대중 납치 사건)]
-
A.
mayExperience
Indicates that an entity is capable of undergoing, feeling, or being subject to a particular event, state, or condition.
-
B.
violationExperienced
Indicates that an entity has been subjected to or has undergone a violation, such as a breach of rights, rules, or agreed standards.
-
C.
experiences
chosen
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
-
D.
trauma
Indicates that an entity has experienced a deeply distressing or harmful event or series of events that cause lasting psychological or emotional impact.
-
E.
incidentWith
Indicates that one entity is involved in, affected by, or associated with a particular incident or event together with another entity.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6375ece288190bec1ca486bbd2f12 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:22 p.m.