Triple
T27768242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Memorial Stadium |
E701662
|
entity |
| Predicate | homeConferenceTeam |
P95015
|
FINISHED |
| Object | Pacific Tigers football team |
—
|
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: Pacific Tigers football team | Statement: [Pacific Memorial Stadium, homeConferenceTeam, Pacific Tigers football team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeConferenceTeam Context triple: [Pacific Memorial Stadium, homeConferenceTeam, Pacific Tigers football team]
-
A.
homeTeamSport
Indicates that a particular sport is the primary or designated sport played by a given home team.
-
B.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
C.
team2Conference
Indicates that a second team (team2) is associated with or belongs to a particular conference.
-
D.
teamConferenceContext
Indicates the context or setting in which a team participates in or is associated with a particular conference or league.
-
E.
associatedTeamConference
chosen
Indicates that an entity is linked to, or belongs to, a specific athletic or organizational conference through its team affiliation.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 4:32 p.m.