Triple
T16544289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surya Bonaly |
E401900
|
entity |
| Predicate | backflipLandingType |
P16151
|
FINISHED |
| Object | one-foot landing |
—
|
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: one-foot landing | Statement: [Surya Bonaly, backflipLandingType, one-foot landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backflipLandingType Context triple: [Surya Bonaly, backflipLandingType, one-foot landing]
-
A.
typeOfLanding
chosen
Indicates the specific kind or category of landing that occurs in a given event or situation.
-
B.
batFlip
Indicates the action of a batter flipping or tossing their bat, typically in a celebratory or expressive manner after a hit.
-
C.
performedBackflipOnOneBlade
Indicates that one entity executed a backflip while balancing on a single blade (e.g., of a skate or similar implement) in relation to another entity or context.
-
D.
landingRecovery
Indicates the process or method by which something is retrieved or secured after it has landed.
-
E.
landingMethod
Indicates the manner or technique by which something or someone arrives and comes to rest at a destination, typically from the air or space.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34560daf08190b353b415d8ab280d |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.