Triple
T8218756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Tech Huskies men's ice hockey |
E192003
|
entity |
| Predicate | hasProducedNHLPlayers |
P66562
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Michigan Tech Huskies men's ice hockey, hasProducedNHLPlayers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProducedNHLPlayers Context triple: [Michigan Tech Huskies men's ice hockey, hasProducedNHLPlayers, true]
-
A.
numberOfBrothersInNHL
Indicates the count of a person's brothers who have played in the NHL.
-
B.
hasProducedPlayersFor
chosen
Indicates that one entity has been the source or origin of players who go on to be associated with, or participate for, another entity.
-
C.
playedInNHLSeasons
Indicates that an individual participated as a player in one or more specified National Hockey League (NHL) seasons.
-
D.
joinedNHL
Indicates that an entity became a member of, or started playing in, the National Hockey League (NHL).
-
E.
numberOfNHLSeasons
Indicates the total count of seasons an entity has participated in the National Hockey League (NHL).
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb7770cee881908ade560d49427895 |
completed | March 31, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.