Triple
T10293034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeastern Huskies football |
E241408
|
entity |
| Predicate | teamNickname |
P5076
|
FINISHED |
| Object | Huskies |
E84188
|
NE 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: Huskies | Statement: [Northeastern Huskies football, teamNickname, Huskies]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Huskies Context triple: [Northeastern Huskies football, teamNickname, Huskies]
-
A.
Huskies
Huskies is the nickname for the University of Saskatchewan’s varsity athletic teams.
-
B.
Huskies
Huskies is the nickname for the University of Washington’s athletic teams, known especially for their prominent football program and strong presence in NCAA Division I sports.
-
C.
Huskies
chosen
Huskies is the nickname for the athletic teams representing Northeastern University in Boston, Massachusetts.
-
D.
Huskies
Huskies is the nickname and mascot for Michigan Technological University’s men’s ice hockey team, representing the school in NCAA competition.
-
E.
Husky
The Husky is a hardy, thick-coated working dog breed originally developed in Arctic regions for pulling sleds and enduring extreme cold.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d46fb08190b7694290692e47dc |
completed | April 7, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71d1c180481909ca9983e14cbb931 |
completed | April 9, 2026, 3:29 a.m. |
Created at: April 6, 2026, 11:42 a.m.