Triple
T38542923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnipeg Goldeyes |
E924882
|
entity |
| Predicate | hasHostedAllStarGame |
P2679
|
FINISHED |
| Object | Northern League All-Star 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: Northern League All-Star Game | Statement: [Winnipeg Goldeyes, hasHostedAllStarGame, Northern League All-Star Game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostedAllStarGame Context triple: [Winnipeg Goldeyes, hasHostedAllStarGame, Northern League All-Star Game]
-
A.
hasOfficiatedAllStarGame
Indicates that the subject has served as an official (e.g., referee or umpire) in at least one All-Star Game.
-
B.
hasAllStarGame
chosen
Indicates that an entity has participated in, hosted, or is otherwise associated with an All-Star Game event.
-
C.
hasChampionshipGames
Indicates that an entity includes, hosts, or is associated with one or more championship-level games or matches.
-
D.
playedInAllStarGameYear
Indicates that the subject participated as a player in an All-Star Game that took place in the specified year.
-
E.
wasAllStarEverySeasonPlayed
Indicates that the entity was selected as an All-Star in every season of their playing career.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 3, 2026, 4:32 p.m.