Triple
T9670598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head Crusher |
E234014
|
entity |
| Predicate | targetOfAction |
P69992
|
FINISHED |
| Object | unsuspecting passersby within the sketch world |
—
|
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: unsuspecting passersby within the sketch world | Statement: [Head Crusher, targetOfAction, unsuspecting passersby within the sketch world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfAction Context triple: [Head Crusher, targetOfAction, unsuspecting passersby within the sketch world]
-
A.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
targetOfIntervention
Indicates that an entity is the object or focus upon which an intervention, treatment, or action is directed.
-
C.
aimedAtBy
chosen
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
D.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
E.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3ec17081908c2da74a1d1f49da |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.