Triple
T21211437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edge City |
E522729
|
entity |
| Predicate | hasCriminalElement |
P143570
|
FINISHED |
| Object | organized crime gangs |
—
|
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: organized crime gangs | Statement: [Edge City, hasCriminalElement, organized crime gangs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCriminalElement Context triple: [Edge City, hasCriminalElement, organized crime gangs]
-
A.
hasCrimeElement
Indicates that a situation, action, or entity involves or contains a component that is legally recognized as part of a crime.
-
B.
hasCriminalCharacter
Indicates that an entity possesses traits, behaviors, or a reputation associated with criminal activity or unlawful conduct.
-
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.
hasCriminalCodeForm
Indicates that something is associated with, represented by, or expressed in a particular criminal code form or format.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7346eb20c8190aeb3c0cc0a24aaf9 |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5fa92a2448190896c022dd27511ad |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 16, 2026, 3:37 p.m.