Triple
T7800402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge University Boat Club |
E180414
|
entity |
| Predicate | boatRaceCrewSize |
P30694
|
FINISHED |
| Object | 8 rowers plus coxswain |
—
|
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: 8 rowers plus coxswain | Statement: [Cambridge University Boat Club, boatRaceCrewSize, 8 rowers plus coxswain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatRaceCrewSize Context triple: [Cambridge University Boat Club, boatRaceCrewSize, 8 rowers plus coxswain]
-
A.
boatRaceRole
Indicates the specific role or function an entity has within the context of a boat race (e.g., participant, organizer, official).
-
B.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
C.
crewCount
chosen
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
-
D.
hasBoatCapacity
Indicates the maximum number of people or amount of load that a boat is designed or allowed to carry.
-
E.
lifeboatCapacity
Indicates the maximum number of people or load that a lifeboat is designed and certified to safely carry.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:33 p.m.