Triple
T22016235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umberto Anastasio |
E543717
|
entity |
| Predicate | predecessorAsBossOfGambinoFamily |
P76270
|
FINISHED |
| Object | Vincent Mangano |
—
|
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: Vincent Mangano | Statement: [Umberto Anastasio, predecessorAsBossOfGambinoFamily, Vincent Mangano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsBossOfGambinoFamily Context triple: [Umberto Anastasio, predecessorAsBossOfGambinoFamily, Vincent Mangano]
-
A.
predecessorRealName
Indicates that one entity is the real (actual) name of the predecessor of another entity.
-
B.
predecessorCEO
Indicates that one person previously held the position of CEO before another specific person.
-
C.
predecessorAsHeadOfClan
chosen
Indicates that one entity previously held the position of head of the clan immediately before the other entity.
-
D.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
E.
predecessorInOfficeOfVictim
Indicates that the subject held a particular office or position immediately before the victim did.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a8a1388190b9e0c1795fe1183a |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:22 p.m.