Triple
T38293836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Rose Bowl |
E1022435
|
entity |
| Predicate | conferenceChampionParticipant |
P33356
|
FINISHED |
| Object | Big Ten champion |
—
|
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: Big Ten champion | Statement: [2019 Rose Bowl, conferenceChampionParticipant, Big Ten champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceChampionParticipant Context triple: [2019 Rose Bowl, conferenceChampionParticipant, Big Ten champion]
-
A.
conferenceChampionAward
Indicates that an entity has received the championship award for winning a specific conference or league competition.
-
B.
eventParticipant
chosen
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
C.
participantWith
Indicates that an entity takes part in an event, activity, or process together with another specified entity.
-
D.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
E.
conferenceHost
Indicates that an entity serves as the organizer or host responsible for running or managing a conference for 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:30 p.m.