Triple
T28155280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OUBC |
E714724
|
entity |
| Predicate | boatRaceOrganiserRole |
P74512
|
FINISHED |
| Object | represents Oxford in The Boat Race |
—
|
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: represents Oxford in The Boat Race | Statement: [OUBC, boatRaceOrganiserRole, represents Oxford in The Boat Race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatRaceOrganiserRole Context triple: [OUBC, boatRaceOrganiserRole, represents Oxford in The Boat Race]
-
A.
boatRaceRole
chosen
Indicates the specific role or function an entity has within the context of a boat race (e.g., participant, organizer, official).
-
B.
boatRaceVenue
Indicates the location or venue where a boat race takes place.
-
C.
roleInRacingCalendar
Indicates the specific function or significance that a race or event holds within the overall racing calendar or season schedule.
-
D.
conferenceRowing
Indicates a relationship where a conference event or organization is engaged in, hosting, or associated with the sport or activity of rowing.
-
E.
notableRegattaType
Indicates that the subject is notably associated with, or characterized by participation in, a particular type or class of regatta.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 10:02 p.m.