Triple
T2210250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Red |
E50898
|
entity |
| Predicate | endedAsStLouisCardinals |
P36800
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Big Red, endedAsStLouisCardinals, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedAsStLouisCardinals Context triple: [Big Red, endedAsStLouisCardinals, 1987]
-
A.
establishedAsStLouisCardinals
Indicates that an entity was formally founded, designated, or recognized as the St. Louis Cardinals organization or team.
-
B.
team2RelocatedToCurrentCity
Indicates that the second team has moved its location to the city where it is currently based.
-
C.
affiliatedWithMLBTeam
Indicates that an entity has an official association or partnership with a Major League Baseball (MLB) team, such as ownership, operation, or formal organizational linkage.
-
D.
ballparkFormerName
Indicates that one name was previously used as the official name of a particular ballpark before it was changed.
-
E.
CubsPreviousTitle
Indicates that one entity is a previous title or designation that the other entity (the Cubs) held or was known by before its current title.
- F. None of above. chosen
Provenance (4 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfce5abc8190b90b92e32045385d |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf0c2b8881908553eed5be17a9c2 |
completed | March 7, 2026, 6 a.m. |
Created at: March 4, 2026, 7:46 p.m.