Triple
T21652720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonel John "Hannibal" Smith |
E534377
|
entity |
| Predicate | crimeAccusation |
P144878
|
FINISHED |
| Object | robbery of the Bank of Hanoi |
—
|
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 the Bank of Hanoi | Statement: [Colonel John "Hannibal" Smith, crimeAccusation, robbery of the Bank of Hanoi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crimeAccusation Context triple: [Colonel John "Hannibal" Smith, crimeAccusation, robbery of the Bank of Hanoi]
-
A.
crimeCharged
Indicates that legal authorities have formally accused an entity of committing a specific crime.
-
B.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
C.
accusationType
Indicates the specific category or nature of an accusation made by one party against another.
-
D.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
E.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
- F. None of above. chosen
Provenance (4 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef591594a08190bf0ddd0a0c0922ba |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:36 p.m.