Triple
T616449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiesta Bowl |
E14414
|
entity |
| Predicate | conferenceTieIn |
P16666
|
FINISHED |
| Object | at-large teams |
—
|
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: at-large teams | Statement: [Fiesta Bowl, conferenceTieIn, at-large teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceTieIn Context triple: [Fiesta Bowl, conferenceTieIn, at-large teams]
-
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.
conference2
Indicates that one entity is a conference or event that is associated with, hosted by, or otherwise related to another entity.
-
D.
conference1
Indicates a relationship where an entity is associated with, participates in, or is characterized as a specific conference event or instance.
-
E.
conferenceAlignment
Indicates how closely a conference’s themes, goals, or content correspond to a particular standard, interest, or strategic objective.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e22f3688190a512bec3f0347814 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49d76062c819083ac33f1f87097c7 |
completed | March 1, 2026, 8:11 p.m. |
Created at: March 1, 2026, 7:35 p.m.