Triple
T1384953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luzon Strait |
E29822
|
entity |
| Predicate | navigationHazard |
P22896
|
FINISHED |
| Object | strong winds and rough seas during typhoon 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: strong winds and rough seas during typhoon season | Statement: [Luzon Strait, navigationHazard, strong winds and rough seas during typhoon season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationHazard Context triple: [Luzon Strait, navigationHazard, strong winds and rough seas during typhoon season]
-
A.
hasNavigationHazard
chosen
Indicates that something presents or contains a condition, object, or feature that poses a risk or obstacle to safe navigation.
-
B.
hasNavigationHazardRelevance
Indicates that something is relevant to, affected by, or poses a potential hazard to navigation.
-
C.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
D.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
E.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33896548190b44f70c9aaaed9b6 |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.