Triple
T34388288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennesaw State Owls |
E882617
|
entity |
| Predicate | sponsoredSports |
P179151
|
FINISHED |
| Object | baseball |
—
|
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: baseball | Statement: [Kennesaw State Owls, sponsoredSports, baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsoredSports Context triple: [Kennesaw State Owls, sponsoredSports, baseball]
-
A.
sportsSponsored
Indicates that one entity provides financial or material sponsorship to support another entity’s sports-related activities or events.
-
B.
sponsorSport
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
-
C.
alsoSponsorsSport
Indicates that an entity that sponsors one sport also sponsors another sport.
-
D.
sportsAttraction
Indicates a relationship where an entity serves as a venue, site, or draw specifically for sports-related activities or events.
-
E.
sportFocus
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
- F. None of above. chosen
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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:59 a.m.