Triple
T37135886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DiMeo crime family |
E919962
|
entity |
| Predicate | hasActingBoss |
P192683
|
FINISHED |
| Object | Junior Soprano |
E268692
|
NE 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: Junior Soprano | Statement: [DiMeo crime family, hasActingBoss, Junior Soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActingBoss Context triple: [DiMeo crime family, hasActingBoss, Junior Soprano]
-
A.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
-
B.
hasCentralBoss
Indicates that an entity is under the authority or control of a primary, central boss figure.
-
C.
isBossIn
Indicates that one entity holds a boss or supervisory role over another entity within a specific context or organization.
-
D.
isBoss
Indicates that one entity holds a supervisory or managerial authority over another entity in a hierarchical structure.
-
E.
isAfterBoss
Indicates that one entity occurs or is positioned later in sequence or time than the boss entity.
- F. None of above. chosen
Provenance (5 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f6a2773ac8190928c55ab86886f55 |
completed | June 27, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 3, 2026, 4:15 p.m.