Triple
T260651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Cora |
E5532
|
entity |
| Predicate | suspendedForSeason |
P10026
|
FINISHED |
| Object | 2020 MLB season |
—
|
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: 2020 MLB season | Statement: [Alex Cora, suspendedForSeason, 2020 MLB season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suspendedForSeason Context triple: [Alex Cora, suspendedForSeason, 2020 MLB season]
-
A.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
-
B.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
-
C.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
D.
adjournedFor
Indicates that an event, meeting, or proceeding has been paused or suspended for a specified duration or until a particular time or condition is met.
-
E.
notableSeason
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b6c968c819094fc903a3a377e15 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25e292fdc8190bfd51d8848f9ed58 |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.