Triple
T34980274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Bend Blue Sox |
E1008793
|
entity |
| Predicate | playedSeasonRange |
P73853
|
FINISHED |
| Object | 1943–1954 |
—
|
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: 1943–1954 | Statement: [South Bend Blue Sox, playedSeasonRange, 1943–1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedSeasonRange Context triple: [South Bend Blue Sox, playedSeasonRange, 1943–1954]
-
A.
playedSeasonType
Indicates that an entity participated in or was involved with a particular type of season (e.g., regular season, playoffs, preseason) within a competition or schedule.
-
B.
careerSeasons
Indicates the number or set of seasons during which an entity actively participated in a particular career or professional role.
-
C.
teamSeasonParticipated
Indicates that a team took part in a particular sports season.
-
D.
sportNumberOfSeasonsInLeague
Indicates the total count of seasons an entity has participated in a particular sports league.
-
E.
playedFromSeason
chosen
Indicates the starting season from which an entity (such as a player or participant) began playing for or being active with another entity (such as a team or organization).
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:01 p.m.