Triple
T33580377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah State Aggies |
E860132
|
entity |
| Predicate | notableAlumnusInFootball |
P10392
|
FINISHED |
| Object | Merlin Olsen |
E51696
|
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: Merlin Olsen | Statement: [Utah State Aggies, notableAlumnusInFootball, Merlin Olsen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAlumnusInFootball Context triple: [Utah State Aggies, notableAlumnusInFootball, Merlin Olsen]
-
A.
notableCoachAlumnus
Indicates that a person is a notable former player or trainee of a particular coach.
-
B.
notableAthleteFrom
Indicates that an athlete is notably associated with or originates from a particular place or region.
-
C.
notableAlumniAchievement
Indicates that an alumnus is recognized for a significant achievement or distinction associated with their post-graduation activities.
-
D.
notableAthlete
chosen
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
E.
hallOfFameAlumnus
Indicates that an individual is recognized as a Hall of Fame member associated with a particular institution, organization, or group.
- F. None of above.
Provenance (4 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35afe373f88190abc1119522549c35 |
completed | June 19, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:40 a.m.