Triple

T5915271
Position Surface form Disambiguated ID Type / Status
Subject Buffalo Bisons (Major League) E131563 entity
Predicate featuredProminentPlayers P18052 FINISHED
Object true 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: true | Statement: [Buffalo Bisons (Major League), featuredProminentPlayers, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: featuredProminentPlayers
Context triple: [Buffalo Bisons (Major League), featuredProminentPlayers, true]
  • A. featuresTopPlayersFrom
    Indicates that something includes or showcases the most prominent or best-performing players from a specified source or group.
  • B. featuresTopPlayers chosen
    Indicates that something prominently presents or showcases the most outstanding or highly ranked players.
  • C. hasNotablePlayer
    Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
  • D. featuresPlayersFrom
    Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
  • E. featuresPlayer
    Indicates that something includes or prominently presents a particular player as part of its content or composition.
  • 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_69c008593a44819081a07ae0efe6c574 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c048fc112c8190b905bf561c9de096 completed March 22, 2026, 7:54 p.m.
PD Predicate disambiguation batch_69c03352208c8190968efed05a9fd416 completed March 22, 2026, 6:22 p.m.
Created at: March 22, 2026, 3:59 p.m.