Triple
T3953210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surya Bonaly |
E84914
|
entity |
| Predicate | performedBackflipOnOneBlade |
P53099
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Surya Bonaly, performedBackflipOnOneBlade, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedBackflipOnOneBlade Context triple: [Surya Bonaly, performedBackflipOnOneBlade, true]
-
A.
batFlip
Indicates the action of a batter flipping or tossing their bat, typically in a celebratory or expressive manner after a hit.
-
B.
hasStunts
Indicates that one entity performs, includes, or is associated with stunt actions for another entity or context.
-
C.
ridingSpecialty
Indicates that one entity has a particular area of expertise or focus related to riding (e.g., a specific riding style, discipline, or type).
-
D.
performedStandUpOn
Indicates that one entity conducted or participated in a stand-up meeting on a specific date or occasion with respect to another entity.
-
E.
flightAbility
Indicates the capability or potential of an entity to fly or engage in powered or unpowered aerial movement.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefaa3c6a08190bfe76629c7c98eea |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:30 p.m.