Triple
T16162659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 NFC Championship Game |
E392214
|
entity |
| Predicate | PackersRegularSeasonRecord |
P66382
|
FINISHED |
| Object | 10–6 |
—
|
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: 10–6 | Statement: [2010 NFC Championship Game, PackersRegularSeasonRecord, 10–6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PackersRegularSeasonRecord Context triple: [2010 NFC Championship Game, PackersRegularSeasonRecord, 10–6]
-
A.
GreenBayRegularSeasonRecord
chosen
Indicates the win-loss (and possibly tie) record achieved by the Green Bay team during a specific regular season.
-
B.
ChicagoPackersSeason
Indicates the relationship between the Chicago Packers team and a specific basketball season in which they competed.
-
C.
EaglesRegularSeasonRecord
Indicates the win-loss (and possibly tie) performance of the Eagles during a specific regular season.
-
D.
nflRecord
Indicates the win-loss-tie performance record a team or individual has accumulated in NFL competition.
-
E.
teamGreenBayDivision
Indicates that a team is in the same division as the Green Bay football team within a sports league.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e5ffba88190b9dc7bb9afb6fdf2 |
completed | April 17, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:02 a.m.