Triple
T32585620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion of Boom |
E832912
|
entity |
| Predicate | keyGameResult |
P10213
|
FINISHED |
| Object | Seattle Seahawks 43–8 Denver Broncos |
—
|
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: Seattle Seahawks 43–8 Denver Broncos | Statement: [Legion of Boom, keyGameResult, Seattle Seahawks 43–8 Denver Broncos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyGameResult Context triple: [Legion of Boom, keyGameResult, Seattle Seahawks 43–8 Denver Broncos]
-
A.
gameOutcome
chosen
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
B.
keyGame
Indicates a relationship where a key is associated with, used in, or required for a particular game or game-related context.
-
C.
kickoffGameResult
Indicates the outcome or result associated with the kickoff event in a game or match.
-
D.
playerOutcome
Indicates the result or consequence experienced by a player in a game, match, or scenario (such as winning, losing, or drawing).
-
E.
teamOutcome
Indicates the result or consequence experienced by a team as a whole in relation to a specific event, activity, or performance.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c66d08708190809cadede7084f54 |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.