Triple
T22056385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Flair vs. Asuka |
E545022
|
entity |
| Predicate | finishMove |
P146430
|
FINISHED |
| Object | Figure-Eight Leglock |
—
|
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: Figure-Eight Leglock | Statement: [Charlotte Flair vs. Asuka, finishMove, Figure-Eight Leglock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishMove Context triple: [Charlotte Flair vs. Asuka, finishMove, Figure-Eight Leglock]
-
A.
finishPosition
Indicates the final rank or place an entity achieves in an ordered outcome, such as a race, competition, or sequence of results.
-
B.
finishSetting
Indicates that an entity completes configuring or establishing a particular setting or set of settings for another entity or context.
-
C.
endOfMovement
Indicates the point or moment at which a movement, action, or motion comes to a stop or is completed.
-
D.
finishOption
Indicates that one entity represents a way, method, or configuration by which another entity is completed, finalized, or brought to its end state.
-
E.
finishType
Indicates the manner or outcome by which an action, process, or event 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128588e0081909056ac8251afe935 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:26 p.m.