Triple
T34099419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1978 Gator Bowl incident |
E874521
|
entity |
| Predicate | conferenceTeamInvolved |
P116792
|
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: [1978 Gator Bowl incident, conferenceTeamInvolved, Big Ten Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceTeamInvolved Context triple: [1978 Gator Bowl incident, conferenceTeamInvolved, Big Ten Conference]
-
A.
conferenceTeam1
Indicates that an entity participates in or is associated with the first team in a conference-related context.
-
B.
conference2Team
chosen
Indicates that a team is associated with or participates in a particular conference.
-
C.
teamsParticipated
Indicates that the referenced teams took part in a particular event, activity, or competition.
-
D.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
-
E.
teamParticipated
Indicates that a team took part in or was involved in a particular event, activity, or 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:53 a.m.