Triple
T28573995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lufthansa heist |
E723184
|
entity |
| Predicate | involvedGang |
P111221
|
FINISHED |
| Object | Lucchese crime family crew based in Queens |
—
|
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: Lucchese crime family crew based in Queens | Statement: [Lufthansa heist, involvedGang, Lucchese crime family crew based in Queens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedGang Context triple: [Lufthansa heist, involvedGang, Lucchese crime family crew based in Queens]
-
A.
associatedWithGang
chosen
Indicates that an entity has a known or alleged connection, membership, or involvement with a gang.
-
B.
roleInGangRelated
Indicates that an entity holds a specific role or function within a gang-related context or activity.
-
C.
associatedWithFictionalGang
Indicates a relationship where an entity is linked or connected to a fictional gang, such as by membership, affiliation, or notable involvement.
-
D.
roleInGang
Indicates that an entity holds a specific position or function within a gang organization.
-
E.
maskUsedByGang
Indicates that a particular mask is used by a specific gang.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 28, 2026, 4:11 a.m.