Triple

T36543638
Position Surface form Disambiguated ID Type / Status
Subject Fast5 Netball World Series E901084 entity
Predicate hasOfficialRules P6248 FINISHED
Object Fast5 ruleset defined by World Netball 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: Fast5 ruleset defined by World Netball | Statement: [Fast5 Netball World Series, hasOfficialRules, Fast5 ruleset defined by World Netball]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOfficialRules
Context triple: [Fast5 Netball World Series, hasOfficialRules, Fast5 ruleset defined by World Netball]
  • A. hasRulebook chosen
    Indicates that one entity possesses, is governed by, or is associated with a specific rulebook.
  • B. hasOfficial
    Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
  • C. hasSpecialRules
    Indicates that certain entities are governed by additional or exceptional rules that differ from the standard ones.
  • D. areOfficialIn
    Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
  • E. hasVenueRules
    Indicates that specific rules or policies are associated with, or apply to, a particular venue.
  • 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_69f76e61217081908b79d610fe67b013 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcec5f8b448190b48330a19b462d24 completed May 7, 2026, 7:47 p.m.
PD Predicate disambiguation batch_69fceaf1e23881908ca24160a638e329 completed May 7, 2026, 7:41 p.m.
Created at: May 3, 2026, 4:11 p.m.