Triple
T442067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Wolverines football |
E10133
|
entity |
| Predicate | bowlAppearances |
P11245
|
FINISHED |
| Object | numerous |
—
|
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: numerous | Statement: [Michigan Wolverines football, bowlAppearances, numerous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bowlAppearances Context triple: [Michigan Wolverines football, bowlAppearances, numerous]
-
A.
hasBowlAppearances
chosen
Indicates that an entity has participated in one or more bowl game appearances.
-
B.
clubAppearances
Indicates the number of official matches a player has played for a particular club.
-
C.
allStarAppearances
Indicates the number of times an entity has been selected to participate in an All-Star event or game.
-
D.
runnerUpConsecutiveAppearances
Indicates that an entity has achieved runner-up status in a competition for a specified number of consecutive appearances or editions.
-
E.
playoffAppearances
Indicates the number of times an entity (such as a team or player) has qualified for and participated in postseason playoff competition.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef42b4008190abed9d79926c7022 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2edde2b9c8190bd20b582eb4c5065 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.