Triple
T21445952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford sewing machinists |
E529074
|
entity |
| Predicate | strikeAction |
P144377
|
FINISHED |
| Object | walkout at Dagenham plant |
—
|
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: walkout at Dagenham plant | Statement: [Ford sewing machinists, strikeAction, walkout at Dagenham plant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strikeAction Context triple: [Ford sewing machinists, strikeAction, walkout at Dagenham plant]
-
A.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
B.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
C.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
D.
spinAttackEffect
Indicates an effect that occurs when an entity performs or is subjected to a spinning attack action.
-
E.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b707ecd88190b3576b8923840870 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63d2aca38819094d312078feaa436 |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 16, 2026, 6:05 p.m.