Triple
T34844117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minneapolis Regional |
E1004420
|
entity |
| Predicate | tournamentDivision |
P178553
|
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: [Minneapolis Regional, tournamentDivision, Division I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentDivision Context triple: [Minneapolis Regional, tournamentDivision, Division I]
-
A.
gameDivision
Indicates a hierarchical or categorical separation of a game into distinct parts, sections, or groups.
-
B.
tournamentSection
chosen
Indicates that an entity is a specific section, division, or bracket within a larger tournament.
-
C.
conferenceDivisionStructureUsed
Indicates that a particular conference employs a specific divisional structure to organize its constituent groups or competitions.
-
D.
divisionChampionship
Indicates that an entity has won a championship title within a specific competitive division or group.
-
E.
divisionOfConference
Indicates that one entity is a division or subgroup within a larger conference organization or 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.