Triple
T10803276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas A&M Aggies women’s basketball |
E254896
|
entity |
| Predicate | hasScholarshipAthletes |
P95547
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Texas A&M Aggies women’s basketball, hasScholarshipAthletes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScholarshipAthletes Context triple: [Texas A&M Aggies women’s basketball, hasScholarshipAthletes, true]
-
A.
footballScholarshipsAllowed
Indicates that the rules or conditions permit the granting or use of football-related scholarships.
-
B.
studentAthletes
Indicates a relationship where the entities are athletes who are also enrolled as students, combining academic and athletic roles.
-
C.
collegeAthleteIn
Indicates that an individual is an athlete who competes for or represents a particular college or university.
-
D.
hasOrganScholarships
Indicates that an entity offers or provides scholarships specifically related to organ study or performance.
-
E.
hasScholarships
Indicates that an entity provides, offers, or is associated with one or more scholarships to another 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7336feff88190b638b7d62d34da0e |
completed | April 9, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:18 p.m.