Triple
T5051882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriot League |
E113803
|
entity |
| Predicate | offersAthleticScholarships |
P11489
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Patriot League, offersAthleticScholarships, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersAthleticScholarships Context triple: [Patriot League, offersAthleticScholarships, yes]
-
A.
associatedScholarship
Indicates a relationship where a scholarship is linked or connected to a particular entity (such as a person, program, or institution).
-
B.
hasOrganScholarships
Indicates that an entity offers or provides scholarships specifically related to organ study or performance.
-
C.
hasScholarships
chosen
Indicates that an entity provides, offers, or is associated with one or more scholarships to another entity.
-
D.
collegeAthleteIn
Indicates that an individual is an athlete who competes for or represents a particular college or university.
-
E.
studentAthletes
Indicates a relationship where the entities are athletes who are also enrolled as students, combining academic and athletic roles.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7426fc8081908a8227f73168c235 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.