Triple
T6615967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigham Young Cougars football team |
E149350
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Cougars |
E550490
|
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: Cougars | Statement: [Brigham Young Cougars football team, nickname, Cougars]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cougars Context triple: [Brigham Young Cougars football team, nickname, Cougars]
-
A.
Cougars
Cougars is the athletic nickname and mascot for the College of Charleston’s sports teams.
-
B.
Cougars
Cougars are the athletic teams and spirit symbol representing Chicago State University in collegiate sports.
-
C.
Cougars
The Cougars are the athletic teams representing the University of Minnesota Morris in intercollegiate sports.
-
D.
Cougars
Cougars is the nickname and mascot for the University of Houston’s athletic teams, representing the school in collegiate sports.
-
E.
Cougars
chosen
The Cougars are the athletic teams representing Brigham Young University, known especially for their competitive NCAA Division I sports programs.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6af57fd748190bb64f1965bab319f |
completed | March 27, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cbda469481908173db345ba2f216 |
completed | March 27, 2026, 6:26 p.m. |
Created at: March 27, 2026, 1:57 p.m.