Triple
T6152127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cable Street |
E137227
|
entity |
| Predicate | organizedAgainst |
P33291
|
FINISHED |
| Object | planned fascist march |
—
|
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: planned fascist march | Statement: [Battle of Cable Street, organizedAgainst, planned fascist march]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedAgainst Context triple: [Battle of Cable Street, organizedAgainst, planned fascist march]
-
A.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
-
B.
organizedInResponseTo
Indicates that an action or event was arranged or carried out specifically as a reaction to a prior situation, event, or stimulus.
-
C.
organizedAs
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
D.
advocatesAgainst
chosen
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
-
E.
organizedDuring
Indicates that an event or activity was arranged or took place within a specified time period or temporal 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cfe20408190b5ec9b987e1a4206 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.