Triple
T613406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sugar Bowl |
E12148
|
entity |
| Predicate | traditionalConferenceTieIn |
P17120
|
FINISHED |
| Object | SEC 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: SEC champion | Statement: [Sugar Bowl, traditionalConferenceTieIn, SEC champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalConferenceTieIn Context triple: [Sugar Bowl, traditionalConferenceTieIn, SEC champion]
-
A.
conferenceType
Indicates the specific category or kind of conference associated with an entity (e.g., workshop, symposium, seminar).
-
B.
conferenceAtTheTime
Indicates that an event or situation occurs during the time period in which a specified conference is taking place.
-
C.
conference1
Indicates a relationship where an entity is associated with, participates in, or is characterized as a specific conference event or instance.
-
D.
conferenceAlignment
Indicates how closely a conference’s themes, goals, or content correspond to a particular standard, interest, or strategic objective.
-
E.
otherConference
Indicates that one conference is distinct from and not the same as another conference.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e08dbf88190ab050078a63e266b |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49def31ec81909dc53e70f4a36eda |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.