Triple
T8440945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omar Little |
E199348
|
entity |
| Predicate | notableHeist |
P37389
|
FINISHED |
| Object | robbery of Barksdale stash houses |
—
|
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: robbery of Barksdale stash houses | Statement: [Omar Little, notableHeist, robbery of Barksdale stash houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHeist Context triple: [Omar Little, notableHeist, robbery of Barksdale stash houses]
-
A.
notableTheft
chosen
Indicates that an entity is involved in a theft event that is widely recognized or significant in some notable way.
-
B.
notableHeistTarget
Indicates that an entity is a significant or high-profile target of a heist or major theft.
-
C.
notableSuspect
Indicates that an individual is a particularly significant or prominent suspect in relation to an event, case, or investigation.
-
D.
notableCartel
Indicates that an entity is recognized as a significant or prominent drug cartel within its context.
-
E.
notableAce
Indicates that one entity is a particularly distinguished or outstanding example (an “ace”) within the domain or activity associated with the other entity.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.