Triple
T18403200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Monarchs |
E450048
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Dominion University athletic program nickname |
C40463
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Old Dominion University athletic program nickname Context triple: [Lady Monarchs, instanceOf, Old Dominion University athletic program nickname]
-
A.
Purdue University nickname
The Purdue University nickname represents the informal moniker or set of monikers (such as "Boilermakers") commonly used to identify and refer to Purdue University, its athletic teams, and its community.
-
B.
University of Kentucky sports team
The University of Kentucky sports team is an athletic organization representing the University of Kentucky in intercollegiate competitions across various sports, most notably its nationally recognized men's basketball and football programs.
-
C.
University of Richmond sports team
The University of Richmond sports team is an organized collegiate athletic program representing the University of Richmond in intercollegiate competitions across various sports.
-
D.
athletic conference nickname
An athletic conference nickname is an informal, often shortened or stylized name used to refer to a collegiate or professional sports conference in a recognizable and memorable way.
-
E.
Duke University school
A Duke University school is an academic division within Duke University that offers specialized undergraduate, graduate, and professional programs, integrating teaching, research, and service in a particular field of study.
- F. None of above. chosen
Provenance (1 batch)
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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:46 a.m.