Triple
T11876335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blunder Bowl |
E282535
|
entity |
| Predicate | associatedWithFinalScore |
P2625
|
FINISHED |
| Object | Baltimore Colts 16–13 Dallas Cowboys |
—
|
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: Baltimore Colts 16–13 Dallas Cowboys | Statement: [Blunder Bowl, associatedWithFinalScore, Baltimore Colts 16–13 Dallas Cowboys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFinalScore Context triple: [Blunder Bowl, associatedWithFinalScore, Baltimore Colts 16–13 Dallas Cowboys]
-
A.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
B.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
C.
scoredFor
Indicates that one entity achieved points or a score on behalf of another entity, such as a player scoring for a team.
-
D.
scoredBy
Indicates that a particular score, point, or result was achieved or obtained by a specific entity.
-
E.
coScoredWith
Indicates that two or more entities received the same score or were evaluated with an identical scoring outcome in a shared context.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.