Triple
T35859042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slab of Bacon trophy |
E1036590
|
entity |
| Predicate | lostAfter |
P64517
|
FINISHED |
| Object | 1943 Wisconsin–Minnesota game |
—
|
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: 1943 Wisconsin–Minnesota game | Statement: [Slab of Bacon trophy, lostAfter, 1943 Wisconsin–Minnesota game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostAfter Context triple: [Slab of Bacon trophy, lostAfter, 1943 Wisconsin–Minnesota game]
-
A.
lostAfterDiscovery
Indicates that something ceased to be possessed or went missing after it had already been found or discovered.
-
B.
lostDuring
chosen
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
-
C.
lost
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
-
D.
lostOn
Indicates that one entity was defeated by or failed against another entity in a competitive or comparative context.
-
E.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
- 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_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.