Triple
T5043647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Asphalt Jungle (role as Dix Handley) |
E113606
|
entity |
| Predicate | heistPlan |
P21187
|
FINISHED |
| Object | meticulously planned jewel robbery |
—
|
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: meticulously planned jewel robbery | Statement: [The Asphalt Jungle (role as Dix Handley), heistPlan, meticulously planned jewel robbery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heistPlan Context triple: [The Asphalt Jungle (role as Dix Handley), heistPlan, meticulously planned jewel robbery]
-
A.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
B.
notableTheft
Indicates that an entity is involved in a theft event that is widely recognized or significant in some notable way.
-
C.
allegedPlots
Indicates that one entity is accused or suspected of planning or conspiring to carry out harmful or illicit actions involving another entity.
-
D.
partOfPlan
Indicates that one entity is included as a component or step within a broader plan or strategy.
-
E.
centralPlotDevice
chosen
Indicates that one entity functions as the main narrative mechanism or element around which the plot of the other entity is structured.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fc04f08190aba851fa0192d0fb |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.