Triple
T26948605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2001 Boston Red Sox season |
E678717
|
entity |
| Predicate | homeOpeningOpponent |
P106971
|
FINISHED |
| Object | Baltimore Orioles |
—
|
NE NERFINISHED |
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: Baltimore Orioles | Statement: [2001 Boston Red Sox season, homeOpeningOpponent, Baltimore Orioles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeOpeningOpponent Context triple: [2001 Boston Red Sox season, homeOpeningOpponent, Baltimore Orioles]
-
A.
homeTeamNextOpponent
Indicates that a given team is scheduled to play against a specified opponent in its next home game.
-
B.
teamOpponent
chosen
Indicates that two teams are competing against each other as opponents in a game or match.
-
C.
playoffOpponent
Indicates that two entities are matched to compete against each other in a playoff round or series.
-
D.
homeOpeningDayResult
Indicates the outcome or result of a team's opening day game played at their home venue.
-
E.
recordOpponent
Indicates that one entity is documented or registered as the opposing party or competitor of another entity.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6208771048190b83c9a08156095eb |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:23 a.m.