Triple
T29037721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa Bay Bowl Association |
E737909
|
entity |
| Predicate | formerEventNameManaged |
P65
|
FINISHED |
| Object | Outback Bowl |
E1355820
|
NE 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: Outback Bowl | Statement: [Tampa Bay Bowl Association, formerEventNameManaged, Outback Bowl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerEventNameManaged Context triple: [Tampa Bay Bowl Association, formerEventNameManaged, Outback Bowl]
-
A.
typeOfEventManaged
Indicates that an entity is responsible for organizing, overseeing, or handling a specific category or kind of event.
-
B.
existedBeforeEvent
Indicates that the subject entity was already in existence prior to the occurrence of the specified event.
-
C.
renamedAfterEvent
Indicates that an entity has changed its name as a consequence of, or in commemoration of, a specific event.
-
D.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
E.
formationEvent
Indicates the event or process through which something comes into existence, is created, or is initially established.
- F. None of above.
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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26614069b481909a6ebee4ae9e0122 |
completed | June 8, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 28, 2026, 9:59 a.m.