Triple
T8260457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UND Fighting Hawks |
E193177
|
entity |
| Predicate | nicknameChangeReason |
P2136
|
FINISHED |
| Object | NCAA policy on Native American mascots and imagery |
—
|
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: NCAA policy on Native American mascots and imagery | Statement: [UND Fighting Hawks, nicknameChangeReason, NCAA policy on Native American mascots and imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameChangeReason Context triple: [UND Fighting Hawks, nicknameChangeReason, NCAA policy on Native American mascots and imagery]
-
A.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
B.
reasonForNickname
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
C.
nameChangeDescribedIn
Indicates that a change of name for an entity is documented or specified within a particular source or description.
-
D.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
E.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb793479d08190bd0dd8740bebff95 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.