Triple
T18988300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006 NFL season |
E464612
|
entity |
| Predicate | kickoffGameResult |
P134040
|
FINISHED |
| Object | Pittsburgh Steelers 28, Miami Dolphins 17 |
—
|
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: Pittsburgh Steelers 28, Miami Dolphins 17 | Statement: [2006 NFL season, kickoffGameResult, Pittsburgh Steelers 28, Miami Dolphins 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kickoffGameResult Context triple: [2006 NFL season, kickoffGameResult, Pittsburgh Steelers 28, Miami Dolphins 17]
-
A.
ProBowlResult
Indicates the outcome or performance result of an entity (such as a player or team) in a specific Pro Bowl game.
-
B.
arenaBowlResult
Indicates the outcome or final result of an ArenaBowl game for a given team or participant.
-
C.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
-
D.
gameWinningKicker
Indicates that an entity serves as the kicker responsible for securing the decisive, game-winning score in a contest.
-
E.
bowlGameResult
Indicates the outcome of a specific bowl game, typically linking the game to the competing teams and the final result (such as winner, loser, and score).
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6618ab881909c0ed94930e42e68 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:01 p.m.