Triple
T35421851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butter Bridge |
E1023815
|
entity |
| Predicate | targetPlatformingSkill |
P196769
|
FINISHED |
| Object | precision jumping |
—
|
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: precision jumping | Statement: [Butter Bridge, targetPlatformingSkill, precision jumping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPlatformingSkill Context triple: [Butter Bridge, targetPlatformingSkill, precision jumping]
-
A.
hasPlatformingStyle
chosen
Indicates that one entity features or employs the specific platforming style characterized by the other entity.
-
B.
sportsSkill
Indicates that an entity possesses a particular ability, proficiency, or level of competence in performing a sport or sports-related activity.
-
C.
targetPlatformFeature
Indicates that a particular feature is available on, or specifically associated with, a given target platform.
-
D.
skillType
Indicates the specific category or kind of skill that characterizes or classifies an associated skill-related entity or action.
-
E.
occursOnPlatform
Indicates that an event, action, or process takes place or is carried out on a specified platform.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 3, 2026, 4:03 p.m.