Triple
T16515899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham Iron |
E401182
|
entity |
| Predicate | playoffBerthClinched |
P11176
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Birmingham Iron, playoffBerthClinched, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffBerthClinched Context triple: [Birmingham Iron, playoffBerthClinched, 2019]
-
A.
playoffQualification
chosen
Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
-
B.
wonPlayoffs
Indicates that a team or player emerged as the overall victor in a playoff series or postseason competition.
-
C.
playoffChampionAdvancesTo
Indicates that the team winning a playoff championship progresses to the next specified stage, round, or competition.
-
D.
playoffAchievement
Indicates that an entity has reached or accomplished a specific milestone or result in a playoff competition or postseason series.
-
E.
playoffTrophyContested
Indicates that a particular playoff trophy is the object of competition in a given playoff series or tournament.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7bbfa481909037148cdb4d8996 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.