Triple
T27805555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Lawrence Saints |
E702366
|
entity |
| Predicate | hasDivisionIProgramIn |
P185196
|
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: [St. Lawrence Saints, hasDivisionIProgramIn, men's ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDivisionIProgramIn Context triple: [St. Lawrence Saints, hasDivisionIProgramIn, men's ice hockey]
-
A.
foundedAsDivisionIProgram
Indicates that an organization or team was originally established as a Division I program at the time of its founding.
-
B.
NCAAfullDivisionIImembership
Indicates that an institution holds full, official membership status in NCAA Division II.
-
C.
joinedNCAADivisionI
Indicates that an entity became a member of the NCAA Division I athletic classification.
-
D.
transitionedToDivisionI
Indicates that an entity changed its athletic classification or status to compete at the NCAA Division I level.
-
E.
foundedAsDivisionIIIProgram
Indicates that an organization, typically a sports program or team, was originally established competing at the NCAA Division III level.
- F. None of above. chosen
Provenance (4 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: April 27, 2026, 5:38 p.m.