Triple
T35809285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angle Slam |
E1035183
|
entity |
| Predicate | finishingSequence |
P184667
|
FINISHED |
| Object | often preceded by ankle lock attempts |
—
|
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: often preceded by ankle lock attempts | Statement: [Angle Slam, finishingSequence, often preceded by ankle lock attempts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishingSequence Context triple: [Angle Slam, finishingSequence, often preceded by ankle lock attempts]
-
A.
finishingMethod
Indicates the technique or process used to complete or finalize an object, task, or work.
-
B.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
C.
finishSetting
Indicates that an entity completes configuring or establishing a particular setting or set of settings for another entity or context.
-
D.
finalWorkInSeries
Indicates that one work is the concluding or last installment within a series of related works.
-
E.
finishOptions
Indicates that one entity specifies or controls the possible ways in which another entity can be completed, finalized, or brought to an end.
- F. None of above. chosen
Provenance (4 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:06 p.m.