Triple
T32016000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mob Song |
E817540
|
entity |
| Predicate | incitesEvent |
P138161
|
FINISHED |
| Object | attack on the Beast’s castle |
—
|
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: attack on the Beast’s castle | Statement: [The Mob Song, incitesEvent, attack on the Beast’s castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incitesEvent Context triple: [The Mob Song, incitesEvent, attack on the Beast’s castle]
-
A.
instigates
chosen
Indicates that one entity initiates, provokes, or sets in motion an action, event, or response in another.
-
B.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
C.
inspiredEvent
Indicates that one event served as the motivation, cause, or creative stimulus for another event to occur or be conceived.
-
D.
riotOccurred
Indicates that a riot took place at a specific time and/or location, involving disorderly or violent group behavior.
-
E.
incidentWith
Indicates that one entity is involved in, affected by, or associated with a particular incident or event together with 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b43ae168819098c9774e3634b47a |
completed | May 3, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:16 a.m.