Triple
T1328002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 World Series |
E28373
|
entity |
| Predicate | MarlinsRegularSeasonRecord |
P10319
|
FINISHED |
| Object | 91–71 |
—
|
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: 91–71 | Statement: [2003 World Series, MarlinsRegularSeasonRecord, 91–71]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MarlinsRegularSeasonRecord Context triple: [2003 World Series, MarlinsRegularSeasonRecord, 91–71]
-
A.
marlinsCEOEndYear
Indicates the year in which a person's tenure as CEO of the Marlins ended.
-
B.
hasBuccaneersRegularSeasonRecord
Indicates the regular-season win-loss-tie record achieved by the Tampa Bay Buccaneers.
-
C.
marlinsCEOStartYear
Indicates the year in which an individual began serving as the CEO of the Miami Marlins.
-
D.
NLTeamRegularSeasonRecord
chosen
Indicates the win–loss (and often tie) performance record of a National League baseball team over a regular season.
-
E.
seasonRecord
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c1d8188190b15a641a08345adc |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.