Triple
T26346709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolling Thunder |
E662793
|
entity |
| Predicate | involvesSomersault |
P132818
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rolling Thunder, involvesSomersault, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesSomersault Context triple: [Rolling Thunder, involvesSomersault, yes]
-
A.
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.
-
B.
backflipStatus
Indicates whether an entity is currently performing, has performed, or is expected to perform a backflip action.
-
C.
aerobaticDiscipline
Indicates that an entity is associated with, practices, or specializes in a particular form or category of aerobatic activity or performance.
-
D.
hasStunts
Indicates that one entity performs, includes, or is associated with stunt actions for another entity or context.
-
E.
postFlightSaltos
chosen
Indicates performing one or more salto (flip) maneuvers immediately after landing from a flight phase.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 26, 2026, 10:42 p.m.