Triple
T10232997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivy League athletics |
E243389
|
entity |
| Predicate | footballScholarshipsAllowed |
P92887
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Ivy League athletics, footballScholarshipsAllowed, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footballScholarshipsAllowed Context triple: [Ivy League athletics, footballScholarshipsAllowed, no]
-
A.
scholarshipLimitRelativeToFBS
Indicates a relationship where a scholarship limit is defined or constrained in comparison to the scholarship limits used in the Football Bowl Subdivision (FBS).
-
B.
hasOrganScholarships
Indicates that an entity offers or provides scholarships specifically related to organ study or performance.
-
C.
hasScholarships
Indicates that an entity provides, offers, or is associated with one or more scholarships to another entity.
-
D.
playedCollegeSport
Indicates that the subject participated in an organized college-level sport for the object institution.
-
E.
collegeAthleteIn
Indicates that an individual is an athlete who competes for or represents a particular college or university.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d23a9c4c8190abece9e52879c479 |
completed | April 7, 2026, 9:45 a.m. |
Created at: April 6, 2026, 11:20 a.m.