Triple
T16864241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wapping dispute |
E409996
|
entity |
| Predicate | unionAction |
P95602
|
FINISHED |
| Object | picketing of Wapping 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: picketing of Wapping plant | Statement: [Wapping dispute, unionAction, picketing of Wapping plant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionAction Context triple: [Wapping dispute, unionAction, picketing of Wapping plant]
-
A.
UnionAction
chosen
Indicates actions taken collectively by a labor union, such as strikes, negotiations, or protests, in pursuit of workers’ shared interests.
-
B.
unionForces
Indicates that multiple forces are combined into a single, unified force acting together.
-
C.
unionForm
Indicates that an entity is a form, document, or process used to establish, join, or manage membership in a union or union-related organization.
-
D.
union
Indicates that two or more sets are combined into a single set containing all elements that belong to at least one of them.
-
E.
unionEvent
Indicates an event in which two or more entities are joined or combined into a single unified whole.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b505a390819097ec31cd210eca60 |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.