Triple
T27882468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unione Siciliana (Brooklyn) |
E705127
|
entity |
| Predicate | tiedTo |
P163250
|
FINISHED |
| Object | Mafia activities in Brooklyn |
—
|
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: Mafia activities in Brooklyn | Statement: [Unione Siciliana (Brooklyn), tiedTo, Mafia activities in Brooklyn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tiedTo Context triple: [Unione Siciliana (Brooklyn), tiedTo, Mafia activities in Brooklyn]
-
A.
tiedTo
chosen
Indicates that one entity is physically or figuratively fastened, bound, or otherwise constrained in connection to another entity.
-
B.
tieInWith
Indicates that one thing is connected, coordinated, or made consistent with another, often as part of a combined plan, theme, or schedule.
-
C.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
D.
lifecycleTiedTo
Indicates that the existence, duration, or validity of one entity is dependent on and ends with the lifecycle of another entity.
-
E.
bindsTo
Indicates that one entity physically or functionally attaches or connects to another, often with some specificity or selectivity in the interaction.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:30 p.m.