Triple

T6000347
Position Surface form Disambiguated ID Type / Status
Subject 1914 Boston Braves E133578 entity
Predicate midseasonStanding P41792 FINISHED
Object last place on July 4, 1914 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: last place on July 4, 1914 | Statement: [1914 Boston Braves, midseasonStanding, last place on July 4, 1914]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: midseasonStanding
Context triple: [1914 Boston Braves, midseasonStanding, last place on July 4, 1914]
  • A. isMidseasonExhibition
    Indicates that an event is a special exhibition or showcase taking place in the middle of a regular season or series.
  • B. halftimeScore
    Indicates the score or result of a game or match at the halfway point (halftime).
  • C. usesRegularSeasonStandingsFor
    Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
  • D. leagueStandingDescribed chosen
    Indicates that a particular description or statement expresses or explains a team's position or ranking within a league's standings.
  • E. hasStandings
    Indicates that an entity possesses or is associated with a set of rankings, positions, or status levels within a competitive or comparative context.
  • 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_69c00872444c8190bfaf1739dcec765c completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04ee5e7bc8190aaa87605fa7b102e completed March 22, 2026, 8:19 p.m.
PD Predicate disambiguation batch_69c049e152e88190979ab80cb9b50321 completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:05 p.m.