Triple
T11734640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Wolverines |
E278993
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Wolverines |
E55536
|
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: Wolverines | Statement: [Michigan Wolverines, nickname, Wolverines]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wolverines Context triple: [Michigan Wolverines, nickname, Wolverines]
-
A.
Wolverines
Wolverines is the nickname for the athletic teams representing Utah Valley University in collegiate sports.
-
B.
Wolverines
Wolverines is the mascot representing Simeon Career Academy’s athletic teams and school spirit.
-
C.
Wolverines
chosen
Wolverines are the fierce, wolverine-themed mascots representing the University of Michigan’s athletic teams, especially its storied football program.
-
D.
Wolverines
Wolverines is the athletics nickname for the sports teams representing Morris Brown College.
-
E.
Wolverines!
"Wolverines!" is an early campaign mission in Call of Duty: Modern Warfare 2 in which players defend a suburban American neighborhood from a large-scale Russian invasion.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4daa7f48190896fc7653e9dd70b |
completed | April 10, 2026, 7:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f0199f595081908c10ecd7dd3900e7 |
completed | April 28, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:41 p.m.