Triple
T35859003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota–Wisconsin football rivalry |
E1036589
|
entity |
| Predicate | formerTrophy |
P143094
|
FINISHED |
| Object | Slab of Bacon |
—
|
NE NERFINISHED |
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: Slab of Bacon | Statement: [Minnesota–Wisconsin football rivalry, formerTrophy, Slab of Bacon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTrophy Context triple: [Minnesota–Wisconsin football rivalry, formerTrophy, Slab of Bacon]
-
A.
trophy
Indicates that one entity is a trophy awarded or possessed in relation to another entity, typically as a result of winning or achieving something.
-
B.
namedAfterTrophy
Indicates that one entity has been given a name derived from or in honor of a particular trophy.
-
C.
isFormerChampionshipTrophyOf
chosen
Indicates that an object previously served as the official championship trophy awarded for a particular competition or title.
-
D.
commemorativeTrophy
Indicates that a trophy exists to honor or memorialize a particular person, event, or achievement.
-
E.
trophyCustodian
Indicates that one entity is responsible for holding, safeguarding, or managing a trophy on behalf of another entity or organization.
- 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_6a0076c0a5c4819088b17b95511b93ed |
completed | May 10, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_6a007638a67c81909c091335142260ab |
completed | May 10, 2026, 12:12 p.m. |
Created at: May 3, 2026, 4:06 p.m.