Triple
T6000346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1914 Boston Braves |
E133578
|
entity |
| Predicate | startedSeasonPosition |
P51004
|
FINISHED |
| Object | last place in National League |
—
|
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: last place in National League | Statement: [1914 Boston Braves, startedSeasonPosition, last place in National League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startedSeasonPosition Context triple: [1914 Boston Braves, startedSeasonPosition, last place in National League]
-
A.
originalSeasonStart
Indicates the date or point in time when a season (such as a sports league or TV series) first began or was originally launched.
-
B.
positionInSeason
chosen
Indicates the specific ordinal placement or ranking of something within the sequence of items in a season.
-
C.
debutedAtPosition
Indicates the initial rank or placement an entity achieved on a specified chart, list, or ranking at the time of its first appearance.
-
D.
beganInLeagueSeason
Indicates that an entity (such as a team, player, or competition) began its participation or activity during a specified league season.
-
E.
startSeason
Indicates the point in time or event at which a particular season begins.
- 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.