Triple

T26388850
Position Surface form Disambiguated ID Type / Status
Subject NBA player E663356 entity
Predicate typicalDraftSource P6625 FINISHED
Object NCAA college basketball 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: NCAA college basketball | Statement: [NBA player, typicalDraftSource, NCAA college basketball]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalDraftSource
Context triple: [NBA player, typicalDraftSource, NCAA college basketball]
  • A. typicalDraft
    Indicates that something represents the standard or commonly expected version or form of a draft within a given context.
  • B. hasTypicalDraftRange
    Indicates the usual or expected range of draft positions at which an entity (such as a player or item) is commonly selected.
  • C. draftedIn
    Indicates that one entity was selected or recruited into another entity (such as a team, organization, or military service) through a formal draft process.
  • D. typicalRosterSource chosen
    Indicates that one entity is the usual or standard source from which the other entity’s roster or list of members is derived.
  • E. draftedFrom
    Indicates that one entity was selected or recruited from another entity, typically as part of a formal drafting or selection process.
  • 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_69ee88374adc81909868f3bab374a32f completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69fe9b0276d48190b554fa22b043e6d8 completed May 9, 2026, 2:25 a.m.
PD Predicate disambiguation batch_69fe999692b081909921e1148d66f0ef completed May 9, 2026, 2:19 a.m.
Created at: April 26, 2026, 11:24 p.m.