Triple
T35806726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Ride |
E1035119
|
entity |
| Predicate | finisherType |
P183796
|
FINISHED |
| Object | powerbomb variant |
—
|
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: powerbomb variant | Statement: [Last Ride, finisherType, powerbomb variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finisherType Context triple: [Last Ride, finisherType, powerbomb variant]
-
A.
finisher
Indicates that an entity completes, concludes, or brings to an end a process, event, or sequence, often as the final actor or decisive contributor.
-
B.
finisherCategory
chosen
Indicates the classification or type assigned to how something is finished or completed (e.g., style, method, or outcome of a finishing action).
-
C.
finisherFor
Indicates that one entity serves as the concluding or final component, action, or step for another entity.
-
D.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
E.
finishingMethod
Indicates the technique or process used to complete or finalize an object, task, or work.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.