Triple
T13447095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antigua Sailing Week |
E320510
|
entity |
| Predicate | typicalWindConditions |
P74831
|
FINISHED |
| Object | trade wind sailing |
—
|
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: trade wind sailing | Statement: [Antigua Sailing Week, typicalWindConditions, trade wind sailing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWindConditions Context triple: [Antigua Sailing Week, typicalWindConditions, trade wind sailing]
-
A.
typicalWindStrength
Indicates the usual or characteristic intensity of wind associated with something, such as a place, time, or condition.
-
B.
windCharacteristics
chosen
Indicates the specific properties or qualities that describe the behavior and nature of the wind in a given context.
-
C.
windSpeed
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
D.
prevailingSurfaceWinds
Indicates the typical or most frequently occurring wind direction and speed that dominate at a given location over a specified period.
-
E.
typicalWeatherNorthernHemisphere
Indicates the characteristic or commonly occurring weather conditions found in the Northern Hemisphere.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef758b08190b9aa5ec7082cd417 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.