Triple
T3879725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri Valley Conference |
E92789
|
entity |
| Predicate | notableSportStrength |
P5150
|
FINISHED |
| Object | men's basketball |
—
|
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: men's basketball | Statement: [Missouri Valley Conference, notableSportStrength, men's basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSportStrength Context triple: [Missouri Valley Conference, notableSportStrength, men's basketball]
-
A.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
B.
knownForSports
chosen
Indicates that an entity is recognized or notable for its involvement, achievement, or association with sports.
-
C.
notableLeague
Indicates that there is a significant or prominent league associated with the subject entity.
-
D.
highSchoolSportStrength
Indicates that a particular sport is characterized by a high level of physical strength in the context of high school athletics.
-
E.
notableStatistic
Indicates that a particular statistic is especially significant or noteworthy in relation to the subject.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.