Triple
T15516746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA beach volleyball |
E368852
|
entity |
| Predicate | scholarshipsType |
P2134
|
FINISHED |
| Object | athletic scholarships |
—
|
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: athletic scholarships | Statement: [NCAA beach volleyball, scholarshipsType, athletic scholarships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scholarshipsType Context triple: [NCAA beach volleyball, scholarshipsType, athletic scholarships]
-
A.
scholarshipType
chosen
Indicates the specific category or kind of scholarship associated with an entity.
-
B.
associatedScholarship
Indicates a relationship where a scholarship is linked or connected to a particular entity (such as a person, program, or institution).
-
C.
hasOrganScholarships
Indicates that an entity offers or provides scholarships specifically related to organ study or performance.
-
D.
hasScholarships
Indicates that an entity provides, offers, or is associated with one or more scholarships to another entity.
-
E.
scholarshipEquivalency
Indicates that one scholarship is considered equal in value, coverage, or benefit to another scholarship or financial award.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04033303c8190a87b6384f68a6921 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:02 a.m.