Triple
T939841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Athletic Conference |
E20279
|
entity |
| Predicate | sponsorsGender |
P7453
|
FINISHED |
| Object | men's sports |
—
|
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: men's sports | Statement: [American Athletic Conference, sponsorsGender, men's sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorsGender Context triple: [American Athletic Conference, sponsorsGender, men's sports]
-
A.
sponsors
Indicates that one entity provides financial or material support to another, often in exchange for association, promotion, or fulfillment of certain activities or goals.
-
B.
sportGender
chosen
Indicates that a sport or sporting event is associated with a particular gender category (e.g., men's, women's, mixed).
-
C.
alsoSponsorsSport
Indicates that an entity that sponsors one sport also sponsors another sport.
-
D.
sponsoringOrganizationType
Indicates the kind or category of organization that provides sponsorship or support in the described relationship or activity.
-
E.
sponsorType
Indicates the specific role or category of sponsorship that an entity provides in relation to another entity or event.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b38b7da08190ac0853655dab678a |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.