Triple
T29373537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther Football, LLC |
E744922
|
entity |
| Predicate | homeStadiumOfOwnedTeam |
P2696
|
FINISHED |
| Object | Bank of America Stadium |
—
|
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: Bank of America Stadium | Statement: [Panther Football, LLC, homeStadiumOfOwnedTeam, Bank of America Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumOfOwnedTeam Context triple: [Panther Football, LLC, homeStadiumOfOwnedTeam, Bank of America Stadium]
-
A.
homeStadiumTeam
Indicates that a particular stadium serves as the designated home venue for a specific sports team.
-
B.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
C.
homeStadiumOfTeamTheySupport
Indicates that a stadium is the primary home venue of the team that a person or group supports.
-
D.
homeStadiumOf
chosen
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
E.
homeStadiumNamedAfter
Indicates that a stadium serving as a team's home venue bears the name of a specified person, organization, or entity.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 2:29 p.m.