Triple
T25824672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti H-Block party |
E650493
|
entity |
| Predicate | formedAroundEvent |
P46126
|
FINISHED |
| Object | 1981 hunger strikes |
—
|
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: 1981 hunger strikes | Statement: [Anti H-Block party, formedAroundEvent, 1981 hunger strikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedAroundEvent Context triple: [Anti H-Block party, formedAroundEvent, 1981 hunger strikes]
-
A.
formationEvent
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
B.
posedAtEvent
Indicates that an entity assumed a particular pose or posture during a specified event.
-
C.
shapedByEvent
Indicates that something’s form, state, or characteristics are influenced or determined by a particular event.
-
D.
organizedAround
chosen
Indicates that something is structured, arranged, or centered with respect to a particular focus, principle, or organizing element.
-
E.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 22, 2026, 7:32 a.m.