Triple
T26498328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sean Jones |
E669345
|
entity |
| Predicate | threatenedBy |
P956
|
FINISHED |
| Object |
Eddie Kim
Eddie Kim is a fictional crime boss and primary antagonist in the film "Snakes on a Plane," responsible for orchestrating the deadly plot against witness Sean Jones.
|
E668117
|
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: Eddie Kim | Statement: [Sean Jones, threatenedBy, Eddie Kim]
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: Eddie Kim Triple: [Sean Jones, threatenedBy, Eddie Kim]
Generated description
Eddie Kim is a fictional crime boss and primary antagonist in the film "Snakes on a Plane," responsible for orchestrating the deadly plot against witness Sean Jones.
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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61358da60819085a4be177f30ac99 |
completed | May 2, 2026, 3:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12130fa43481908d9d42c150461606 |
completed | May 23, 2026, 8:50 p.m. |
| NEDg | Description generation | batch_6a1215de625081909e5c3e7bc1be4186 |
completed | May 23, 2026, 9:02 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a1216850b6c8190a5cfaf5dfbffe878 |
completed | May 23, 2026, 9:05 p.m. |
Created at: April 27, 2026, 1:10 a.m.