Triple
T22617267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windermere Cup rowing regatta |
E558180
|
entity |
| Predicate | typicalDateRelation |
P4137
|
FINISHED |
| Object | coincides with Opening Day of Seattle boating season |
—
|
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: coincides with Opening Day of Seattle boating season | Statement: [Windermere Cup rowing regatta, typicalDateRelation, coincides with Opening Day of Seattle boating season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDateRelation Context triple: [Windermere Cup rowing regatta, typicalDateRelation, coincides with Opening Day of Seattle boating season]
-
A.
typicalDates
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
-
B.
typicalEndRelation
Indicates that one event, state, or process is the usual or characteristic endpoint or outcome of another.
-
C.
dateOfRelatedEvent
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
D.
temporalRelation
chosen
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
-
E.
dateRelativeTo
Indicates a temporal relationship where one date is defined, positioned, or interpreted in relation to another reference date (e.g., before, after, or offset by a specific duration).
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f167eeb220819082c90a8bd3cadc4c |
completed | April 29, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:59 p.m.