Triple
T24599502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa Bay Sports and Entertainment |
E608780
|
entity |
| Predicate | primaryVenueForOperations |
P5921
|
FINISHED |
| Object | Amalie Arena |
—
|
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: Amalie Arena | Statement: [Tampa Bay Sports and Entertainment, primaryVenueForOperations, Amalie Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVenueForOperations Context triple: [Tampa Bay Sports and Entertainment, primaryVenueForOperations, Amalie Arena]
-
A.
primaryVenueFor
chosen
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
B.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
C.
operatesVenue
Indicates that one entity manages and runs the day-to-day operations of a particular venue.
-
D.
primaryOperation
Indicates the main or most important operation performed or used by an entity in a given context.
-
E.
operatedEstablishmentIn
Indicates that an entity ran or managed an establishment located within a specified place or jurisdiction.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:30 a.m.