Triple

T15985526
Position Surface form Disambiguated ID Type / Status
Subject Japan Basketball League E387681 entity
Predicate isInCompetitionPyramid P13495 FINISHED
Object Japanese basketball league system 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: Japanese basketball league system | Statement: [Japan Basketball League, isInCompetitionPyramid, Japanese basketball league system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInCompetitionPyramid
Context triple: [Japan Basketball League, isInCompetitionPyramid, Japanese basketball league system]
  • A. statusInCompetition
    Indicates the current standing or role an entity holds within a specific competition or contest.
  • B. hasCompetitionContext
    Indicates that an entity is associated with or occurs within a specific competitive setting, event, or environment.
  • C. usesCompetitionSystem chosen
    Indicates that an entity operates under or applies a particular competition system or format.
  • D. hasCompetitionScope
    Indicates the extent or boundaries within which a competition, contest, or competitive activity is defined or applies.
  • E. hasCompetitionElement
    Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
  • 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_69d86daa562c81908aacc179c0fe8fb5 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e17d4d08f481909f38b75e3f42d9ab completed April 17, 2026, 12:22 a.m.
PD Predicate disambiguation batch_69e142d9d8e881909b559a3e3ca21d24 completed April 16, 2026, 8:13 p.m.
Created at: April 10, 2026, 4:54 a.m.