Triple

T37898966
Position Surface form Disambiguated ID Type / Status
Subject World Surf League Championship Tour E945354 entity
Predicate hasScoringBasis P195069 FINISHED
Object judged maneuvers on waves 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: judged maneuvers on waves | Statement: [World Surf League Championship Tour, hasScoringBasis, judged maneuvers on waves]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasScoringBasis
Context triple: [World Surf League Championship Tour, hasScoringBasis, judged maneuvers on waves]
  • A. hasScoringUnit
    Indicates that one entity possesses or is associated with a unit used for scoring, measurement, or point allocation in a given context.
  • B. hasScorer
    Indicates that one entity serves as the scorer (e.g., the one who scores points, goals, or evaluations) in relation to another entity.
  • C. hasScoreBy
    Indicates that one entity possesses or is associated with a score that was assigned, produced, or determined by another entity.
  • D. hasScoreAvailable
    Indicates that a score or rating for the relevant entity is present and can be accessed.
  • E. isScoreFor
    Indicates that one value represents the score or result associated with a particular entity, event, or performance.
  • 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_69f76ef0e8708190987c7254ed8c7abe completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd9ff026a48190bfec33deeb3b2c43 completed May 8, 2026, 8:33 a.m.
PD Predicate disambiguation batch_69fd97d805bc8190ba12f429d3ad04c7 completed May 8, 2026, 7:59 a.m.
PDg Predicate description generation batch_69fd9fef7aac819089cc88dd3d00296d completed May 8, 2026, 8:33 a.m.
Created at: May 3, 2026, 4:19 p.m.