Triple
T25371104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska–Anchorage rivalry |
E632932
|
entity |
| Predicate | team2Institution |
P144348
|
FINISHED |
| Object | University of Alaska Anchorage |
—
|
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: University of Alaska Anchorage | Statement: [Alaska–Anchorage rivalry, team2Institution, University of Alaska Anchorage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team2Institution Context triple: [Alaska–Anchorage rivalry, team2Institution, University of Alaska Anchorage]
-
A.
teamInstitution
chosen
Indicates that a team is formally associated with, represents, or is part of a particular institution.
-
B.
institutionalAffiliationTeam1
Indicates that an entity is formally affiliated with or belongs to the first team of an institution.
-
C.
primaryVenueTeam2
Indicates that the second team is the main or designated home team for a particular venue.
-
D.
homeTeamUniversity
Indicates that a specified university serves as the home institution or host team in a given game, match, or sporting event.
-
E.
team2Affiliation
Indicates that an entity is affiliated with, belongs to, or is associated with a second team in a given context.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a11323e08190a8ec4687f8fefe7f |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:38 p.m.