Triple
T32366028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redmen |
E826992
|
entity |
| Predicate | usedByAthleticDivision |
P11735
|
FINISHED |
| Object | NCAA Division I |
—
|
NE NERFINISHED |
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: NCAA Division I | Statement: [Redmen, usedByAthleticDivision, NCAA Division I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByAthleticDivision Context triple: [Redmen, usedByAthleticDivision, NCAA Division I]
-
A.
usedByAthleticAssociation
Indicates that something (such as a facility, rule, or resource) is utilized or employed by an athletic association.
-
B.
competesInDivision
chosen
Indicates that an entity participates in competitive activities within a specified division or tier of a larger organizational or league structure.
-
C.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
D.
memberOfSportsDivision
Indicates that an entity belongs to or is assigned to a specific sports division within an organizational or competitive structure.
-
E.
representsAthleticDepartment
Indicates that one entity serves as the athletic department or sports administration body for another entity.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 12:50 a.m.