Triple
T27024890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Michigan University Marching Band |
E680757
|
entity |
| Predicate | nicknameOfTeamsSupported |
P94046
|
FINISHED |
| Object | Wildcats |
—
|
NE NERFINISHED |
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: Wildcats | Statement: [Northern Michigan University Marching Band, nicknameOfTeamsSupported, Wildcats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameOfTeamsSupported Context triple: [Northern Michigan University Marching Band, nicknameOfTeamsSupported, Wildcats]
-
A.
clubFullNameSupported
Indicates that the complete official name of a club is recognized and supported within the system.
-
B.
teamNameIncludes
Indicates that a team's name contains a specified substring or text fragment.
-
C.
teamNicknamedAfter
Indicates that a team is commonly referred to by a nickname derived from or inspired by another entity.
-
D.
supportsTeamName
chosen
Indicates that one entity provides endorsement, backing, or advocacy for a particular team identified by its name.
-
E.
teamNameType
Indicates the type or category associated with a team's name (e.g., formal name, short name, nickname).
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6223131b0819081deea3d5ed98ea5 |
completed | May 2, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:10 a.m.