Triple
T35527488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sable Splash |
E1026709
|
entity |
| Predicate | finisherCategory |
P183796
|
FINISHED |
| Object | top-rope finisher |
—
|
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: top-rope finisher | Statement: [Sable Splash, finisherCategory, top-rope finisher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finisherCategory Context triple: [Sable Splash, finisherCategory, top-rope finisher]
-
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.
finisherFor
Indicates that one entity serves as the concluding or final component, action, or step for another entity.
-
C.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
D.
finishingMethod
Indicates the technique or process used to complete or finalize an object, task, or work.
-
E.
finishingArea
Indicates the location or area where an activity, process, or event comes to an end or is completed.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:04 p.m.