Triple
T25637226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USC Trojans athletics |
E642738
|
entity |
| Predicate | footballFutureConference |
P152549
|
FINISHED |
| Object | Big Ten Conference |
—
|
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: Big Ten Conference | Statement: [USC Trojans athletics, footballFutureConference, Big Ten Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footballFutureConference Context triple: [USC Trojans athletics, footballFutureConference, Big Ten Conference]
-
A.
homeTeamFutureLeague
chosen
Indicates the league in which the home team is expected or scheduled to compete in the future.
-
B.
awayTeamFutureLeague
Indicates that an away team is associated with a league it will participate in at a future time.
-
C.
leagueConference
Indicates that a sports league is associated with, organized into, or belongs to a particular conference within its competitive structure.
-
D.
nextNFLChampionshipGame
Indicates that one game is the immediately upcoming NFL championship game relative to a given reference time or schedule.
-
E.
nextAFCChampionshipGame
Indicates the relationship where a given entity is the immediately upcoming AFC Championship Game in time.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa6345548190a52498ecb0a2f555 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 5:34 p.m.