Triple

T1112099
Position Surface form Disambiguated ID Type / Status
Subject NBA Draft E11017 entity
Predicate sourceOfPlayers P13374 FINISHED
Object international professional leagues 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: international professional leagues | Statement: [NBA Draft, sourceOfPlayers, international professional leagues]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sourceOfPlayers
Context triple: [NBA Draft, sourceOfPlayers, international professional leagues]
  • A. featuresPlayersFrom
    Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
  • B. primaryPlayerSource chosen
    Indicates that an entity serves as the main origin or provider of a player within a given context or system.
  • C. typicalRosterSource
    Indicates that one entity is the usual or standard source from which the other entity’s roster or list of members is derived.
  • D. governsPlayersFrom
    Indicates that an entity exercises authority or control over players originating from a specified source or group.
  • E. producedLeaguePlayers
    Indicates that an entity has developed or given rise to players who went on to participate in a specified league.
  • 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_69a493252a648190ac48f8742474a5e8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4bbd92a8c8190a16e55f3f739010f completed March 1, 2026, 10:21 p.m.
PD Predicate disambiguation batch_69a4bb42990c819080db96478fd4977e completed March 1, 2026, 10:18 p.m.
Created at: March 1, 2026, 7:43 p.m.