Triple
T38570188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richie Aprile |
E929242
|
entity |
| Predicate | plansCoupAgainst |
P92643
|
FINISHED |
| Object | Tony Soprano |
—
|
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: Tony Soprano | Statement: [Richie Aprile, plansCoupAgainst, Tony Soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansCoupAgainst Context triple: [Richie Aprile, plansCoupAgainst, Tony Soprano]
-
A.
plannedAttackWith
Indicates that one entity has prepared or organized an attack using or involving another entity as the means or instrument of that attack.
-
B.
plansMurdersToMatch
Indicates that an entity devises murders so that they correspond to or align with another pattern, plan, or set of criteria.
-
C.
plannedAttack
chosen
Indicates that an entity has intentionally prepared and organized an attack against a target.
-
D.
plansRobberyOf
Indicates that one entity is planning or preparing to commit a robbery targeting another entity.
-
E.
plansToMurder
Indicates that one entity intends and has formed a plan to unlawfully kill 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.