Triple
T18860501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biles II (vault, Yurchenko double pike) |
E461298
|
entity |
| Predicate | saltoType |
P133204
|
FINISHED |
| Object | double piked salto backward |
—
|
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: double piked salto backward | Statement: [Biles II (vault, Yurchenko double pike), saltoType, double piked salto backward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saltoType Context triple: [Biles II (vault, Yurchenko double pike), saltoType, double piked salto backward]
-
A.
saltMineType
Indicates the specific kind or classification of a salt mine associated with an entity.
-
B.
spurType
Indicates the specific kind or category of spur associated with or used by an entity.
-
C.
springType
Indicates the specific kind or category of spring associated with an entity (e.g., coil, leaf, torsion).
-
D.
slipType
Indicates the specific category or kind of slip involved in an action or relationship between entities.
-
E.
allyType
Indicates that one entity is classified as a specific type or category of ally in relation to another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.