Triple
T26108418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham Stallions |
E658602
|
entity |
| Predicate | madeUSFLSemifinals |
P98949
|
FINISHED |
| Object | 1984 |
—
|
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: 1984 | Statement: [Birmingham Stallions, madeUSFLSemifinals, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeUSFLSemifinals Context triple: [Birmingham Stallions, madeUSFLSemifinals, 1984]
-
A.
semifinalMatchup
Indicates that two competitors or teams are paired to compete against each other in a semifinal round of a tournament or competition.
-
B.
semifinalTeam
chosen
Indicates that an entity is a team that has qualified for and participates in the semifinal round of a competition or tournament.
-
C.
semifinalResult
Indicates the outcome or score of a semifinal-stage contest or match between competitors.
-
D.
semifinalWinner
Indicates that the subject entity has won a semifinal match or round, thereby advancing toward the final stage of a competition.
-
E.
semifinalBowls
Indicates that the entities are the bowl games that serve as semifinal matchups in a tournament or playoff structure.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60779ae4c81909428c6d249cc0665 |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8 p.m.