Triple
T7596847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford University Boat Club |
E179876
|
entity |
| Predicate | boatRaceCourseLocation |
P56309
|
FINISHED |
| Object | between Putney and Mortlake |
—
|
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: between Putney and Mortlake | Statement: [Oxford University Boat Club, boatRaceCourseLocation, between Putney and Mortlake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatRaceCourseLocation Context triple: [Oxford University Boat Club, boatRaceCourseLocation, between Putney and Mortlake]
-
A.
boatRaceRole
Indicates the specific role or function an entity has within the context of a boat race (e.g., participant, organizer, official).
-
B.
waterbodyOnCourse
chosen
Indicates that a waterbody lies along, intersects, or is situated on the path of a particular course, such as a river or stream.
-
C.
canoeingVenue
Indicates that a location serves as a site or facility where canoeing activities take place.
-
D.
boathouseLocation
Indicates the place where a boathouse is situated or located.
-
E.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d4d3408190b9650347c7850c47 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.