Triple
T1438999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockit |
E31024
|
entity |
| Predicate | hasThemeRelation |
P20616
|
FINISHED |
| Object | corruption in law enforcement |
—
|
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: corruption in law enforcement | Statement: [Lockit, hasThemeRelation, corruption in law enforcement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThemeRelation Context triple: [Lockit, hasThemeRelation, corruption in law enforcement]
-
A.
hasThemeConnection
chosen
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
-
B.
containsThemeArea
Indicates that one entity includes or encompasses a specific thematic area as part of its scope or content.
-
C.
hasCentralTheme
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
-
D.
hasPersonalThemes
Indicates that something (such as a work, message, or expression) involves themes that are personal, intimate, or directly related to an individual’s own experiences or inner life.
-
E.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.