Triple
T7888359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kim Dae-jung |
E183159
|
entity |
| Predicate | survivedAssassinationAttempt |
P48637
|
FINISHED |
| Object | 1973 kidnapping in Tokyo |
—
|
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 kidnapping in Tokyo | Statement: [Kim Dae-jung, survivedAssassinationAttempt, 1973 kidnapping in Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivedAssassinationAttempt Context triple: [Kim Dae-jung, survivedAssassinationAttempt, 1973 kidnapping in Tokyo]
-
A.
consequenceOfAssassinationAttempt
Indicates a state, event, or condition that occurs as a direct result of an assassination attempt.
-
B.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
-
C.
assassinated
Indicates that one entity deliberately killed another, typically for political, ideological, or strategic reasons.
-
D.
survivedConflict
chosen
Indicates that an entity continued to live or exist after experiencing and enduring a specific conflict or violent event.
-
E.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39ea8d1c81908ef99569e0cf00b7 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:59 p.m.