Triple
T20219176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SWAC West Division |
E495204
|
entity |
| Predicate | teamsType |
P2705
|
FINISHED |
| Object | historically Black colleges and universities |
—
|
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: historically Black colleges and universities | Statement: [SWAC West Division, teamsType, historically Black colleges and universities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamsType Context triple: [SWAC West Division, teamsType, historically Black colleges and universities]
-
A.
typeOfTeams
chosen
Indicates the categories or kinds of teams to which an entity or group of entities belongs.
-
B.
teamNameType
Indicates the type or category associated with a team's name (e.g., formal name, short name, nickname).
-
C.
teamCodeType
Indicates the classification or category type associated with a particular team code.
-
D.
teamNumberType
Indicates the type or category assigned to a team’s identifying number within a given system or context.
-
E.
teamBasedOn
Indicates that one entity (typically a team) is formed, organized, or defined on the basis of another entity (such as a criterion, source, or underlying structure).
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66edbb67081909c7359ff27205b5f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.