Triple
T37135914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DiMeo crime family |
E919962
|
entity |
| Predicate | operationalTerritory |
P126730
|
FINISHED |
| Object | North Jersey |
E207241
|
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: North Jersey | Statement: [DiMeo crime family, operationalTerritory, North Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalTerritory Context triple: [DiMeo crime family, operationalTerritory, North Jersey]
-
A.
operatesFromTerritory
chosen
Indicates that an entity conducts its activities or operations based out of, or primarily within, a specified territory.
-
B.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
C.
operatesToRegion
Indicates that an agent conducts operations or provides services directed toward or within a specified region.
-
D.
recognizedTerritory
Indicates that one entity formally acknowledges another entity’s claim of authority or ownership over a specific geographic area.
-
E.
operatesInTerritoriesOutside
Indicates that an entity conducts activities or maintains operations in geographic areas beyond its primary or home territories.
- F. None of above.
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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a020243e2b4819086dbfdcf4372405e |
completed | May 11, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f6a2773ac8190928c55ab86886f55 |
completed | June 27, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_6a0200f585bc8190b774c54cec409b00 |
completed | May 11, 2026, 4:16 p.m. |
Created at: May 3, 2026, 4:15 p.m.