Triple
T14656148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifty-Two Pickup |
E344112
|
entity |
| Predicate | featuresOrganizedCrime |
P21640
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fifty-Two Pickup, featuresOrganizedCrime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresOrganizedCrime Context triple: [Fifty-Two Pickup, featuresOrganizedCrime, true]
-
A.
criminalOrganization
chosen
Indicates that the subject is an organized group engaged in ongoing illegal activities, often with structured hierarchy and coordination.
-
B.
criminalType
Indicates the specific category or classification of crime associated with a criminal act or offender.
-
C.
crimeType
Indicates the specific category or nature of the crime associated with an event or entity.
-
D.
recognitionOfCrimes
Indicates the formal acknowledgment or identification that certain actions or events constitute crimes under a legal or normative framework.
-
E.
crimeListedInArticleIII
Indicates that a particular crime is one of the offenses expressly mentioned in Article III of the relevant constitution or legal document.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51a562c819098971447db4b29f7 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.