Triple
T28580628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 NFC Championship |
E723363
|
entity |
| Predicate | vikingsTurnovers |
P164650
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [2009 NFC Championship, vikingsTurnovers, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vikingsTurnovers Context triple: [2009 NFC Championship, vikingsTurnovers, 5]
-
A.
RavensTurnoversForced
Indicates the number of times the Ravens’ defense causes the opposing offense to lose possession of the ball through interceptions, fumbles, or similar plays.
-
B.
turnoversTotal
Indicates the total number of times possession changes from one entity to another, typically due to errors, losses, or rule-based transfers.
-
C.
cowboysTurnovers
Indicates the number of times the Cowboys lose possession of the ball to the opposing team through fumbles or interceptions.
-
D.
coltsTurnovers
Indicates the number of times the Colts lost possession of the ball to the opposing team through turnovers (such as interceptions or fumbles).
-
E.
turnoversForcedByTitans
Indicates the number of turnovers that were caused or forced by the Titans against their opponents.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650cbb3348190977e970d2986a846 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 4:14 a.m.