Triple
T34059299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for the Barrel |
E873445
|
entity |
| Predicate | associatedUniversityTeam2 |
P144348
|
FINISHED |
| Object | University of Louisville |
E102304
|
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: University of Louisville | Statement: [Battle for the Barrel, associatedUniversityTeam2, University of Louisville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedUniversityTeam2 Context triple: [Battle for the Barrel, associatedUniversityTeam2, University of Louisville]
-
A.
collegeTeam
Indicates that one entity is a sports team that represents or is affiliated with a particular college or university.
-
B.
teamInstitution
chosen
Indicates that a team is formally associated with, represents, or is part of a particular institution.
-
C.
associatedSeniorTeam
Indicates a relationship where a senior-level team is linked or connected to a given entity as its corresponding or responsible team.
-
D.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
-
E.
associatedTeamName
Indicates the name of the team that is linked or connected to a given entity.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36e60ae0b481908360dd0182f052b6 |
completed | June 20, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.