Triple
T35859010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota–Wisconsin football rivalry |
E1036589
|
entity |
| Predicate | playedForTrophySince |
P40941
|
FINISHED |
| Object | Paul Bunyan’s Axe 1948 |
—
|
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: Paul Bunyan’s Axe 1948 | Statement: [Minnesota–Wisconsin football rivalry, playedForTrophySince, Paul Bunyan’s Axe 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedForTrophySince Context triple: [Minnesota–Wisconsin football rivalry, playedForTrophySince, Paul Bunyan’s Axe 1948]
-
A.
trophyWonWith
Indicates that a particular trophy or award was achieved using, through, or in association with a specified means, tool, team, or context.
-
B.
trophyWonBy
Indicates that a particular trophy or award is obtained or earned by a specific entity (such as a person or team).
-
C.
hasTrophyStatus
Indicates that an entity possesses a particular trophy-related status or classification.
-
D.
trophyIntroducedInSeason
chosen
Indicates the season in which a particular trophy was first introduced or became part of a competition or series.
-
E.
namedAfterTrophy
Indicates that one entity has been given a name derived from or in honor of a particular trophy.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:06 p.m.