Triple
T37842345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banzai Pipeline |
E943510
|
entity |
| Predicate | recommendedSkillLevel |
P56693
|
FINISHED |
| Object | advanced to professional surfers only |
—
|
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: advanced to professional surfers only | Statement: [Banzai Pipeline, recommendedSkillLevel, advanced to professional surfers only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedSkillLevel Context triple: [Banzai Pipeline, recommendedSkillLevel, advanced to professional surfers only]
-
A.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
B.
requiresSkillLevel
chosen
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
C.
includeSkillLevel
Indicates that a specified skill is associated with an entity together with a particular proficiency or mastery level.
-
D.
servesSkillLevel
Indicates that one entity provides or is appropriate for a particular level of skill in another entity.
-
E.
typicalExperienceLevel
Indicates the usual or most common level of experience associated with an entity in a given context.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.