Triple
T177175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FCS |
E3597
|
entity |
| Predicate | allowsAthleticScholarships |
P54
|
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: [FCS, allowsAthleticScholarships, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsAthleticScholarships Context triple: [FCS, allowsAthleticScholarships, true]
-
A.
allowsNonScholarshipPrograms
Indicates that an entity permits the operation or participation of programs that do not offer scholarships.
-
B.
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).
-
C.
studentAthletes
Indicates a relationship where the entities are athletes who are also enrolled as students, combining academic and athletic roles.
-
D.
scholarshipType
Indicates the specific category or kind of scholarship associated with an entity.
-
E.
hasAthletics
chosen
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258fd278481908ad4498e03f38e2f |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25669d99481908c5e82ba8641205a |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.