Triple
T33540241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCLA Bruins swimming and diving |
E859049
|
entity |
| Predicate | athletesAre |
P17934
|
FINISHED |
| Object | student-athletes |
—
|
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: student-athletes | Statement: [UCLA Bruins swimming and diving, athletesAre, student-athletes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: athletesAre Context triple: [UCLA Bruins swimming and diving, athletesAre, student-athletes]
-
A.
athletesFrom
Indicates that one or more athletes originate from, represent, or are associated with a particular place or organization.
-
B.
hasAthlete
chosen
Indicates a relationship where an entity (such as a team, organization, or event) includes or is associated with one or more athletes.
-
C.
isAthlete
Indicates that an entity participates in sports or athletic activities, typically at a competitive or professional level.
-
D.
oftenShareAthletesWith
Indicates that two entities frequently have the same athletes participating or competing for both of them.
-
E.
typeOfAthlete
Indicates that one entity is an athlete and the other specifies the kind or category of athlete they are.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:39 a.m.