Triple
T1125110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Conference |
E24700
|
entity |
| Predicate | NCAADivisionStatus |
P279
|
FINISHED |
| Object | Division I |
—
|
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: Division I | Statement: [Southern Conference, NCAADivisionStatus, Division I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NCAADivisionStatus Context triple: [Southern Conference, NCAADivisionStatus, Division I]
-
A.
NCAADivision
chosen
Indicates the competitive division within the NCAA in which an institution or team participates.
-
B.
competesInDivision
Indicates that an entity participates in competitive activities within a specified division or tier of a larger organizational or league structure.
-
C.
NCAASport
Indicates that an entity is a sport that is officially sanctioned or governed by the NCAA (National Collegiate Athletic Association).
-
D.
notableDivision
Indicates that one entity is a significant or prominent subdivision, branch, or section of another entity.
-
E.
teamDivision
Indicates how a larger team is split into smaller subgroups or units for organization or collaboration.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4749ac8190b0fbddac2e9b2586 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.