Triple
T26856185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford University Squash Rackets Club |
E676200
|
entity |
| Predicate | varsityOpponent |
P106971
|
FINISHED |
| Object | Cambridge University |
—
|
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: Cambridge University | Statement: [Oxford University Squash Rackets Club, varsityOpponent, Cambridge University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: varsityOpponent Context triple: [Oxford University Squash Rackets Club, varsityOpponent, Cambridge University]
-
A.
teamOpponent
chosen
Indicates that two teams are competing against each other as opponents in a game or match.
-
B.
finalOpponentTeam
Indicates the team that serves as the last or ultimate opposing team faced in a competition, series, or event.
-
C.
rivalTeam
Indicates that one team is in a competitive or adversarial relationship with another team, often vying for superiority or dominance.
-
D.
finalOpponentInstitution
Indicates the institution that served as the final opposing side in a competition, match, or contest involving the subject.
-
E.
rivalConferenceTeams
Indicates that the two teams compete in the same athletic conference and are considered rivals within that conference.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:21 a.m.