Triple
T371903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Ocean |
E8285
|
entity |
| Predicate | experiencesNaturalHazard |
P2854
|
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: [Indian Ocean, experiencesNaturalHazard, tropical cyclones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencesNaturalHazard Context triple: [Indian Ocean, experiencesNaturalHazard, tropical cyclones]
-
A.
experiences
chosen
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
-
B.
facedMajorEarthquake
Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
-
C.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
D.
aftershocks
Indicates that one seismic event occurs as a subsequent, typically smaller tremor following a main earthquake.
-
E.
followsNaturalFeature
Indicates that one entity’s position, path, or boundary runs alongside or is aligned with a natural geographic feature (such as a river, coastline, or ridgeline).
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec00785481908551fc3571fcca47 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.