Triple
T31484599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Rowing Cup |
E803237
|
entity |
| Predicate | typicalNumberOfRegattasPerSeason |
P12655
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [World Rowing Cup, typicalNumberOfRegattasPerSeason, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNumberOfRegattasPerSeason Context triple: [World Rowing Cup, typicalNumberOfRegattasPerSeason, 3]
-
A.
notableRegattaParticipation
Indicates that an entity has taken part in a regatta that is considered notable or significant.
-
B.
notableRegattaType
Indicates that the subject is notably associated with, or characterized by participation in, a particular type or class of regatta.
-
C.
homeRegatta
Indicates that a particular regatta is designated as the home event for a given team, club, or venue.
-
D.
typicalNumberOfMeetingsPerSeason
chosen
Indicates the usual or average count of meetings that occur within a single season.
-
E.
sailingSeries
Indicates a relationship where multiple sailing events or races are grouped together as part of the same organized series or competition.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:34 p.m.