Triple
T5379120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Raiders |
E113035
|
entity |
| Predicate | hasAthleticProgramType |
P63640
|
FINISHED |
| Object | men's teams |
—
|
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 teams | Statement: [Red Raiders, hasAthleticProgramType, men's teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAthleticProgramType Context triple: [Red Raiders, hasAthleticProgramType, men's teams]
-
A.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
B.
parentAthleticProgram
Indicates that one athletic program serves as the overarching or higher-level program to which another athletic program belongs or is subordinate.
-
C.
hasSportsInstitute
Indicates that an entity possesses, hosts, or is associated with a sports institute or sports training facility.
-
D.
hasAthlete
Indicates a relationship where an entity (such as a team, organization, or event) includes or is associated with one or more athletes.
-
E.
typeOfNCAAInvolvement
Indicates the specific way or role in which an entity is involved with or participates in the NCAA.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd887f5b0081909456992d1a071928 |
completed | March 20, 2026, 5:48 p.m. |
Created at: March 20, 2026, 2:03 p.m.