Triple
T24105977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodney Mullen |
E597222
|
entity |
| Predicate | inventedTrick |
P56932
|
FINISHED |
| Object | kickflip |
—
|
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: kickflip | Statement: [Rodney Mullen, inventedTrick, kickflip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inventedTrick Context triple: [Rodney Mullen, inventedTrick, kickflip]
-
A.
performedTrick
Indicates that one entity executed or carried out a trick involving another entity or in a particular context.
-
B.
gimmick
Indicates that an entity uses or features a novel, attention-grabbing trick or device primarily intended to attract interest rather than provide substantive value.
-
C.
invention
chosen
Indicates that one entity is the creator or originator of another entity, typically a device, method, or idea.
-
D.
fictionalInvention
Indicates that one entity is an invention or creation that exists only within the fictional context of another entity (such as a story, universe, or work).
-
E.
usedInventionOf
Indicates that one entity made use of, applied, or implemented the invention created by another entity.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de170ee88190a6d57482651f7da9 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:01 p.m.