Triple
T30672609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Son of a Gun |
E780830
|
entity |
| Predicate | hasHeist |
P178787
|
FINISHED |
| Object | gold heist |
—
|
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: gold heist | Statement: [Son of a Gun, hasHeist, gold heist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeist Context triple: [Son of a Gun, hasHeist, gold heist]
-
A.
hasHeistSequence
chosen
Indicates that an event, narrative, or work includes a planned theft or robbery sequence as a significant part of its action.
-
B.
heistOutcome
Indicates the result or consequence of a heist, such as its success, failure, or specific aftermath.
-
C.
survivesHeist
Indicates that an entity successfully endures and remains unharmed or intact through the course of a heist.
-
D.
notableHeistType
Indicates that the subject is notably associated with a specific type or category of heist.
-
E.
hasSleuth
Indicates that an entity is associated with or employs a sleuth (detective) responsible for investigating on its behalf.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 29, 2026, 8:32 p.m.