Triple
T5611908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Browns Stadium |
E147376
|
entity |
| Predicate | sponsorNameRemoved |
P15098
|
FINISHED |
| Object | FirstEnergy name removed in 2023 |
—
|
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: FirstEnergy name removed in 2023 | Statement: [Cleveland Browns Stadium, sponsorNameRemoved, FirstEnergy name removed in 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorNameRemoved Context triple: [Cleveland Browns Stadium, sponsorNameRemoved, FirstEnergy name removed in 2023]
-
A.
renamingSponsor
Indicates that one entity serves as the sponsor responsible for the renaming of another entity.
-
B.
previousSponsorshipName
chosen
Indicates that an entity had a different sponsorship name in the past, specifying what that prior sponsored name was.
-
C.
sponsorEnded
Indicates that a sponsorship relationship between entities has been terminated or has come to an end.
-
D.
sponsorshipEnded
Indicates that a previously existing sponsorship relationship between entities has been terminated or has come to an end.
-
E.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0211fad448190b068b77ed25931d5 |
completed | March 22, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.