Triple
T6000330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1914 Boston Braves |
E133578
|
entity |
| Predicate | finishedRegularSeasonRecord |
P21379
|
FINISHED |
| Object | 94–59 |
—
|
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: 94–59 | Statement: [1914 Boston Braves, finishedRegularSeasonRecord, 94–59]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishedRegularSeasonRecord Context triple: [1914 Boston Braves, finishedRegularSeasonRecord, 94–59]
-
A.
seasonRecord
chosen
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
B.
regularSeasonEndDate
Indicates the calendar date on which a regular season for a league, competition, or series of events concludes.
-
C.
regularSeasonSuccess
Indicates the degree to which an entity achieves positive outcomes or strong performance during the regular season phase of a competition or activity.
-
D.
runnerUpRegularSeasonRecord
Indicates the regular season performance record (such as wins and losses) of the team that finished as runner-up.
-
E.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
- 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.