Triple
T35479066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edie Doyle |
E1025418
|
entity |
| Predicate | brotherKilledBy |
P183331
|
FINISHED |
| Object | mob-connected union bosses |
—
|
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: mob-connected union bosses | Statement: [Edie Doyle, brotherKilledBy, mob-connected union bosses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brotherKilledBy Context triple: [Edie Doyle, brotherKilledBy, mob-connected union bosses]
-
A.
brothersKilledBy
Indicates that the referenced individuals are brothers who were killed by the same agent or in the same event.
-
B.
sisterMurdered
Indicates that one entity killed the sister of another entity.
-
C.
sonsKilledBy
Indicates that the referenced sons are those who were killed by the specified agent or entity.
-
D.
killedFamilyOf
Indicates that one entity caused the death of one or more members of another entity’s family.
-
E.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
- F. None of above. chosen
Provenance (4 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.