Triple
T27882689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 Rose Bowl |
E705134
|
entity |
| Predicate | conferenceOfOhioState |
P172123
|
FINISHED |
| Object | Big Ten Conference |
—
|
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: Big Ten Conference | Statement: [1976 Rose Bowl, conferenceOfOhioState, Big Ten Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceOfOhioState Context triple: [1976 Rose Bowl, conferenceOfOhioState, Big Ten Conference]
-
A.
coachOhioStateFullName
Indicates that a person serves or served as a coach for the Ohio State team, with their full name specified.
-
B.
homeStadiumWhenOhioStateHosts
Indicates the stadium that serves as the home venue specifically when Ohio State is the hosting team in a game or event.
-
C.
Michigan StateConference
Indicates that a college or university’s athletic programs compete in the same athletic conference as Michigan State University.
-
D.
cityOhioStateHomeGames
Indicates that a city in Ohio is the location where a team plays its home games.
-
E.
ohioStateRecordEnteringGame
Indicates the statistical record held by Ohio State University’s team immediately before a specific game begins.
- F. None of above. chosen
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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 27, 2026, 6:31 p.m.