Triple
T6063129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiree Wave Classic |
E135085
|
entity |
| Predicate | typicalWindStrength |
P68425
|
FINISHED |
| Object | strong |
—
|
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: strong | Statement: [Tiree Wave Classic, typicalWindStrength, strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWindStrength Context triple: [Tiree Wave Classic, typicalWindStrength, strong]
-
A.
windSpeed
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
B.
typicalStormType
Indicates the kind of storm that is most commonly or characteristically associated with a given context or location.
-
C.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
D.
maximumSustainedWinds
Indicates the highest wind speed that is maintained continuously over a specified averaging period, rather than in brief gusts.
-
E.
maximumGusts
Indicates the relationship where a recorded wind gust value represents the highest (maximum) gust observed within a specified time or context.
- F. None of above. chosen
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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05722815081909ee47e8f94b87b3a |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:10 p.m.