Triple
T27081501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chai Wan Typhoon Shelter |
E685607
|
entity |
| Predicate | typicalWeatherRisk |
P14395
|
FINISHED |
| Object | tropical cyclones |
—
|
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: tropical cyclones | Statement: [Chai Wan Typhoon Shelter, typicalWeatherRisk, tropical cyclones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWeatherRisk Context triple: [Chai Wan Typhoon Shelter, typicalWeatherRisk, tropical cyclones]
-
A.
hasSevereWeatherRisk
chosen
Indicates that an entity is exposed to or associated with a high likelihood of severe or hazardous weather conditions.
-
B.
typicalWeatherFeature
Indicates a weather condition or pattern that commonly characterizes a place or time period.
-
C.
typicalWindStrength
Indicates the usual or characteristic intensity of wind associated with something, such as a place, time, or condition.
-
D.
weatherConsideration
Indicates that certain conditions, decisions, or actions take into account or are influenced by the current or expected weather.
-
E.
frostRisk
Indicates the likelihood that conditions will lead to frost forming in a given area or on a given object.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: April 27, 2026, 8:35 a.m.