Triple
T37900065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 Rose Bowl |
E945385
|
entity |
| Predicate | notablePlayerWisconsin |
P108163
|
FINISHED |
| Object | Brooks Bollinger |
E996598
|
NE 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: Brooks Bollinger | Statement: [1999 Rose Bowl, notablePlayerWisconsin, Brooks Bollinger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerWisconsin Context triple: [1999 Rose Bowl, notablePlayerWisconsin, Brooks Bollinger]
-
A.
quarterbackWisconsin
chosen
Indicates that the subject served as a quarterback for a team associated with Wisconsin (such as the University of Wisconsin).
-
B.
notableBowlParticipant
Indicates that an entity has participated in a bowl game in a way considered notable or significant.
-
C.
WisconsinCoach
Indicates a person who serves or has served as a coach for a sports team representing the state or a school in Wisconsin.
-
D.
notableAlumnusInNBA
Indicates that a person is a distinguished former student of an institution who has gone on to play in the NBA.
-
E.
notableAthleteFrom
Indicates that an athlete is notably associated with or originates from a particular place or region.
- F. None of above.
Provenance (4 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410cc4c7c881908926c9cf3e2e76d1 |
completed | June 28, 2026, noon |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.