Triple
T14113211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 AFC Championship Game |
E339696
|
entity |
| Predicate | homeHalftimeLead |
P11635
|
FINISHED |
| Object | 14–10 |
—
|
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: 14–10 | Statement: [1999 AFC Championship Game, homeHalftimeLead, 14–10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeHalftimeLead Context triple: [1999 AFC Championship Game, homeHalftimeLead, 14–10]
-
A.
halftimeScore
chosen
Indicates the score or result of a game or match at the halfway point (halftime).
-
B.
halftimeShow
Indicates a performance or entertainment event that takes place during the intermission between two halves of a game or match.
-
C.
halftimeProducer
Indicates that one entity is the producer responsible for creating or organizing the halftime segment of an event, such as a sports game or show.
-
D.
halftimeSponsor
Indicates a sponsorship relationship where an entity serves as the sponsor of the halftime segment of an event or performance.
-
E.
homeTeamUntil
Indicates that an entity serves as the home team for another entity up to (but not necessarily after) a specified time or event.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600f992c81908133813f2894dcca |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.