Triple
T3968392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Bears–Minnesota Vikings rivalry |
E92269
|
entity |
| Predicate | ChicagoBearsJoinedNFL |
P39326
|
FINISHED |
| Object | 1920 |
—
|
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: 1920 | Statement: [Chicago Bears–Minnesota Vikings rivalry, ChicagoBearsJoinedNFL, 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChicagoBearsJoinedNFL Context triple: [Chicago Bears–Minnesota Vikings rivalry, ChicagoBearsJoinedNFL, 1920]
-
A.
teamOwnerOfChicagoBearsAtTime
Indicates that a person or entity is the owner of the Chicago Bears at a specified point in time.
-
B.
pointsScoredByChicagoBears
Indicates the number of points that were scored by the Chicago Bears in a game or event.
-
C.
mergedIntoNFL
chosen
Indicates that an organization or league ceased to exist independently by being absorbed and incorporated into the National Football League (NFL).
-
D.
ChicagoPackersSeason
Indicates the relationship between the Chicago Packers team and a specific basketball season in which they competed.
-
E.
NFLDebutTeam
Indicates the team for which a player made their first appearance in an NFL game.
- 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_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. |
Created at: March 9, 2026, 3:32 p.m.