Triple
T34234097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hector Salamanca |
E878283
|
entity |
| Predicate | attemptedMurderOf |
P169061
|
FINISHED |
| Object | Gustavo Fring |
—
|
NE NERFINISHED |
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: Gustavo Fring | Statement: [Hector Salamanca, attemptedMurderOf, Gustavo Fring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedMurderOf Context triple: [Hector Salamanca, attemptedMurderOf, Gustavo Fring]
-
A.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
B.
threatenedToKill
Indicates that one entity has made a threat or expressed an intention to kill another entity.
-
C.
plansToMurder
chosen
Indicates that one entity intends and has formed a plan to unlawfully kill another entity.
-
D.
perpetratorOfKilling
Indicates that an entity is the one who carried out or caused a particular killing.
-
E.
typeOfKilling
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710b492f481908ee1b0a76011733c |
completed | May 3, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:56 a.m.