Triple
T20132594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mustangs |
E490932
|
entity |
| Predicate | playsCollegeBasketball |
P75480
|
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: [Mustangs, playsCollegeBasketball, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsCollegeBasketball Context triple: [Mustangs, playsCollegeBasketball, yes]
-
A.
playsCollegeBasketballIn
chosen
Indicates that an individual is a member of and competes for a college or university’s basketball team located at a specified institution or place.
-
B.
playedCollegeBasketballFor
Indicates that a person was a member of and competed for a specific college or university’s basketball team.
-
C.
NCAABasketballClassification
Indicates a classification relationship that assigns a college basketball entity to a specific NCAA basketball category, division, or type.
-
D.
collegeSportsContext
Indicates a relationship, event, or situation that specifically occurs within or is shaped by the environment of college or university sports.
-
E.
playedCollegeSport
Indicates that the subject participated in an organized college-level sport for the object institution.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66763ee908190af64af31b4ca2377 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:31 p.m.