Triple
T8791914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American League playoff teams |
E209185
|
entity |
| Predicate | post2022Change |
P60216
|
FINISHED |
| Object | expanded 12-team MLB playoff field |
—
|
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: expanded 12-team MLB playoff field | Statement: [American League playoff teams, post2022Change, expanded 12-team MLB playoff field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: post2022Change Context triple: [American League playoff teams, post2022Change, expanded 12-team MLB playoff field]
-
A.
updatedIn
chosen
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
B.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
C.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
D.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
E.
changedOn
Indicates that an entity underwent a modification or update at a specific point in time.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8e6e4881909155c40c52bc082c |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:43 p.m.