Triple
T22343525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hate Crime Statistics annual report |
E552332
|
entity |
| Predicate | breakdownBy |
P130188
|
FINISHED |
| Object | bias motivation |
—
|
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: bias motivation | Statement: [Hate Crime Statistics annual report, breakdownBy, bias motivation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakdownBy Context triple: [Hate Crime Statistics annual report, breakdownBy, bias motivation]
-
A.
includesBreakdownsBy
chosen
Indicates that something contains or presents detailed subdivisions or component analyses organized according to a specified criterion or entity.
-
B.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
C.
breakdownLedTo
Indicates that one event or situation of breakdown caused or directly resulted in another event or outcome.
-
D.
breakdownDepictedAs
Indicates that a breakdown or decomposition of something is visually represented or illustrated in some form.
-
E.
brokenBy
Indicates that one entity causes the damage, destruction, or loss of functionality of another entity.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15795b2a881908d6cb8f97443ca17 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.