Triple
T26498335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sean Jones |
E669345
|
entity |
| Predicate | reasonForDanger |
P90247
|
FINISHED |
| Object | testimony against crime boss Eddie Kim |
—
|
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: testimony against crime boss Eddie Kim | Statement: [Sean Jones, reasonForDanger, testimony against crime boss Eddie Kim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDanger Context triple: [Sean Jones, reasonForDanger, testimony against crime boss Eddie Kim]
-
A.
reasonForDangerListing
chosen
Indicates the specific cause or justification for why something has been classified or listed as dangerous.
-
B.
dangerousWhen
Indicates that one entity becomes harmful, risky, or unsafe under the conditions or in the presence of another entity or situation.
-
C.
safetyRationale
Indicates the reasoning or justification provided to explain how and why something is considered safe or made safe.
-
D.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
E.
dangerWarning
Indicates that one entity issues or represents a warning about potential danger associated with another entity or situation.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 1:10 a.m.