Triple
T9928038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuks |
E187971
|
entity |
| Predicate | associatedWithSportsTeams |
P330
|
FINISHED |
| Object | University of Pretoria sports teams |
—
|
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: University of Pretoria sports teams | Statement: [Tuks, associatedWithSportsTeams, University of Pretoria sports teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSportsTeams Context triple: [Tuks, associatedWithSportsTeams, University of Pretoria sports teams]
-
A.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
B.
associatedWithChampionshipTeams
Indicates a relationship where an entity has a connection or involvement with one or more championship-winning teams.
-
C.
roleAtSportsTeam
Indicates the specific position or function an individual holds within a sports team.
-
D.
leagueAffiliationThroughOwnedTeam
Indicates that an entity is affiliated with a league by virtue of owning a team that participates in that league.
-
E.
hasSportsTeam
chosen
Indicates that an entity possesses, sponsors, or is represented by a sports team.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb59d7ad08190982a1584547190bd |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.