Triple
T30635981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota State Mavericks |
E779843
|
entity |
| Predicate | ncaaDivisionIFor |
P279
|
FINISHED |
| Object | men’s ice hockey |
—
|
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: men’s ice hockey | Statement: [Minnesota State Mavericks, ncaaDivisionIFor, men’s ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ncaaDivisionIFor Context triple: [Minnesota State Mavericks, ncaaDivisionIFor, men’s ice hockey]
-
A.
NCAAdivisionSport
Indicates that a particular sport is sanctioned and organized under a specific NCAA competitive division (e.g., Division I, II, or III).
-
B.
joinedNCAADivisionI
Indicates that an entity became a member of the NCAA Division I athletic classification.
-
C.
NCAAdivisionIISuccess
Indicates that an entity has achieved notable success or strong performance within NCAA Division II athletics or competitions.
-
D.
NCAAdivisionIIISuccess
Indicates that an entity has achieved notable success or strong performance within NCAA Division III athletics or competitions.
-
E.
NCAADivision
chosen
Indicates the competitive division within the NCAA in which an institution or team participates.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a51b8d48190a00ac690761716ce |
completed | May 2, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:28 p.m.