Triple
T34374843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Stone |
E882258
|
entity |
| Predicate | attemptedAttackOn |
P154963
|
FINISHED |
| Object | Stormont Parliament Buildings |
—
|
NE NERFINISHED |
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: Stormont Parliament Buildings | Statement: [Michael Stone, attemptedAttackOn, Stormont Parliament Buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedAttackOn Context triple: [Michael Stone, attemptedAttackOn, Stormont Parliament Buildings]
-
A.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
B.
wasAttackedIn
Indicates that an entity experienced an attack that occurred at or within a specified location or context.
-
C.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
-
D.
assaultedBy
Indicates that an entity has been attacked or subjected to violent physical aggression by another entity.
-
E.
perpetratedAttackOn
chosen
Indicates that one entity carried out, organized, or was responsible for an attack directed against another entity.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.