Triple
T6493781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nolan Richardson |
E148103
|
entity |
| Predicate | inSport |
P887
|
FINISHED |
| Object | college 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: college men’s basketball | Statement: [Nolan Richardson, inSport, college men’s basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inSport Context triple: [Nolan Richardson, inSport, college men’s basketball]
-
A.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
-
B.
sportFocus
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
C.
sportsAndRecreation
Indicates a relationship where an entity is associated with, involved in, or designated for sports or recreational activities.
-
D.
sportsModel
Indicates a relationship where an entity is a sports-oriented model or variant of another entity (such as a product, design, or system) optimized or styled for sporting use.
-
E.
sport
chosen
Indicates that an entity participates in, is associated with, or is characterized by a particular athletic activity or game.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06ab6abbc8190a4971ad5a654b0cd |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:53 p.m.