Triple
T25022164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blockade |
E626604
|
entity |
| Predicate | hasAntiWarMessage |
P83346
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Blockade, hasAntiWarMessage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAntiWarMessage Context triple: [Blockade, hasAntiWarMessage, true]
-
A.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
B.
hasLanguageOfProtest
chosen
Indicates that an entity expresses or embodies a language, style, or discourse of protest in relation to another entity or context.
-
C.
stanceOnMilitarism
Indicates an entity’s position, attitude, or viewpoint regarding the use, expansion, or role of military force and institutions.
-
D.
blamesForWar
Indicates that one entity holds another entity responsible for causing or contributing to a war.
-
E.
supportedDuringWar
Indicates that one entity provided assistance, resources, or backing to another entity specifically during a time of war.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:07 a.m.