Triple
T800112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milwaukee Brewers |
E17110
|
entity |
| Predicate | expansionTeamYear |
P905
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [Milwaukee Brewers, expansionTeamYear, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionTeamYear Context triple: [Milwaukee Brewers, expansionTeamYear, 1969]
-
A.
expansionTeamIn
chosen
Indicates that a sports team entered a league or competition as an expansion team in a specified season, year, or context.
-
B.
expansionDraftYear
Indicates the year in which an entity (such as a team or franchise) was created or entered a league through an expansion draft.
-
C.
expansionFromPreviousSeason
Indicates that the current season represents an expansion or enlargement relative to the immediately preceding season.
-
D.
leagueEntryYear
Indicates the year in which an entity first entered or joined a particular league.
-
E.
teamCaptainStartYear
Indicates the year in which an entity first began serving as the captain of a team.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7cb26dc8190bdd3a278b8695873 |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.