Triple
T20863409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushover |
E513682
|
entity |
| Predicate | hasCriminalCharacter |
P142154
|
FINISHED |
| Object | bank robber |
—
|
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: bank robber | Statement: [Pushover, hasCriminalCharacter, bank robber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCriminalCharacter Context triple: [Pushover, hasCriminalCharacter, bank robber]
-
A.
hasHadCriminalConviction
Indicates that an entity has previously been found guilty of a criminal offense through a legal process.
-
B.
hasCrimeElement
Indicates that a situation, action, or entity involves or contains a component that is legally recognized as part of a crime.
-
C.
haveCriminalLaw
Indicates that an entity possesses, applies, or is governed by a system or body of criminal law.
-
D.
hasCrimeGroup
Indicates a relationship where an entity is associated with, belongs to, or is controlled by a particular criminal group or organization.
-
E.
consideredCriminalBy
Indicates that one party regards or classifies another party as a criminal according to its own laws, rules, or judgments.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c45d2ec4819098abbb901b9fcd87 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:44 p.m.