Triple
T31374323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overpeck Park (rowing facility) |
E800247
|
entity |
| Predicate | primaryRacingVenueFor |
P39293
|
FINISHED |
| Object | Columbia University varsity rowing teams |
E387706
|
NE 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: Columbia University varsity rowing teams | Statement: [Overpeck Park (rowing facility), primaryRacingVenueFor, Columbia University varsity rowing teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRacingVenueFor Context triple: [Overpeck Park (rowing facility), primaryRacingVenueFor, Columbia University varsity rowing teams]
-
A.
breedersCupVenue
Indicates the venue or location where a particular Breeders' Cup event is held.
-
B.
notableRaceTrackDepicted
Indicates that a work or representation depicts a race track that is considered notable or significant.
-
C.
sportsVenueFor
chosen
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
D.
holdsTournamentsIn
Indicates that an entity organizes or conducts tournaments at or within a specified location.
-
E.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
- F. None of above.
Provenance (4 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b2d67b548819086e5de88ea4e114a |
completed | June 11, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:18 p.m.