Triple
T18860503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biles II (vault, Yurchenko double pike) |
E461298
|
entity |
| Predicate | twisting |
P90006
|
FINISHED |
| Object | no twist |
—
|
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: no twist | Statement: [Biles II (vault, Yurchenko double pike), twisting, no twist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: twisting Context triple: [Biles II (vault, Yurchenko double pike), twisting, no twist]
-
A.
hasTwist
Indicates that an entity (such as a story, object, or feature) includes an unexpected change, reversal, or surprising element relative to what was previously established or anticipated.
-
B.
twistElement
chosen
Indicates that one entity applies a twisting or rotational deformation to another entity.
-
C.
winding
Indicates that something follows a curving, twisting, or spiral path or shape rather than a straight one.
-
D.
twinning
Indicates that two entities are paired or linked as twins, typically sharing a formally recognized, parallel, or closely matched relationship.
-
E.
twistOffAngle
Indicates the angular amount or orientation by which something is twisted off from its original or reference position.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c060bfc4819092ac591692a6ccd5 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.