Triple
T25001438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperBrawl |
E625728
|
entity |
| Predicate | promotionOwnerDuringRun |
P125149
|
FINISHED |
| Object | Turner Broadcasting System |
—
|
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: Turner Broadcasting System | Statement: [SuperBrawl, promotionOwnerDuringRun, Turner Broadcasting System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionOwnerDuringRun Context triple: [SuperBrawl, promotionOwnerDuringRun, Turner Broadcasting System]
-
A.
promotionOwnerAtTime
chosen
Indicates that a specified entity is the owner or controller of a particular promotion during a given time period.
-
B.
promotionOwnerInvolved
Indicates that the owner of a promotion is directly involved or participating in that promotion-related action or event.
-
C.
runnerUpTeamOwner
Indicates the owner of the team that finished as the runner-up in a competition or league.
-
D.
promotionManager
Indicates that one entity serves as the manager responsible for overseeing or administering the promotion of another entity.
-
E.
programOwner
Indicates that one entity is the primary responsible owner or controller of a particular program associated with another 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:04 a.m.