Triple
T3968380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Bears–Minnesota Vikings rivalry |
E92269
|
entity |
| Predicate | conferenceGamesPerSeasonBetweenTeams |
P53222
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Chicago Bears–Minnesota Vikings rivalry, conferenceGamesPerSeasonBetweenTeams, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceGamesPerSeasonBetweenTeams Context triple: [Chicago Bears–Minnesota Vikings rivalry, conferenceGamesPerSeasonBetweenTeams, 2]
-
A.
conferenceGamesPerTeam
Indicates the number of games each team plays against opponents within its conference.
-
B.
divisionGamesPerSeasonBetweenTeams
Indicates the number of games played per season between two teams within the same division.
-
C.
regularSeasonGamesPerTeam
Indicates the number of games each team plays during the regular season.
-
D.
divisionGamesPerSeason
Indicates the number of games played in a particular division during a single season.
-
E.
hasRegularSeasonGamesAgainst
Indicates that one team or participant plays scheduled, recurring competitive games against another during the regular season.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefac8f7a48190b065487ce090eaf2 |
completed | March 9, 2026, 4:52 p.m. |
Created at: March 9, 2026, 3:32 p.m.