Triple

T25851452
Position Surface form Disambiguated ID Type / Status
Subject 1904 World Series E651220 entity
Predicate isOfficiallyRecognizedByMLB P159349 FINISHED
Object yes 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: yes | Statement: [1904 World Series, isOfficiallyRecognizedByMLB, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isOfficiallyRecognizedByMLB
Context triple: [1904 World Series, isOfficiallyRecognizedByMLB, yes]
  • A. hasInternationalBaseballCenter
    Indicates that an entity possesses or hosts an international baseball center as a facility or designated location.
  • B. notEligiblePathToMLB
    Indicates that there is no valid or qualifying pathway for the subject to reach or participate in Major League Baseball (MLB).
  • C. hasMinorLeagueStatus
    Indicates that an entity holds a classification or designation as belonging to a minor league level within a hierarchical league system.
  • D. isMinorLeagueEquivalentOf
    Indicates that one entity serves as the minor-league or lower-tier counterpart or affiliate of another, typically higher-level, entity.
  • E. hasMLBTeamID
    Indicates that an entity is associated with a specific Major League Baseball (MLB) team identifier.
  • F. None of above. chosen

Provenance (4 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_69e7ab39035c8190be15c8aaee1bb858 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6023b96208190925872085ada10e3 completed May 2, 2026, 1:55 p.m.
PD Predicate disambiguation batch_69f4939148dc81908706cec7d85291bc completed May 1, 2026, 11:50 a.m.
PDg Predicate description generation batch_69f497b8abb88190bb672cf6907c4b8d completed May 1, 2026, 12:08 p.m.
Created at: April 22, 2026, 7:58 a.m.