Triple
T26589957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ram Island Ledge |
E667322
|
entity |
| Predicate | isDangerousIn |
P67787
|
FINISHED |
| Object | stormy weather |
—
|
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: stormy weather | Statement: [Ram Island Ledge, isDangerousIn, stormy weather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDangerousIn Context triple: [Ram Island Ledge, isDangerousIn, stormy weather]
-
A.
dangerousWhen
chosen
Indicates that one entity becomes harmful, risky, or unsafe under the conditions or in the presence of another entity or situation.
-
B.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
C.
isInDanger
Indicates that an entity is exposed to a significant risk of harm, loss, or adverse consequences.
-
D.
inDangerSince
Indicates that an entity has been in a state of danger continuously starting from a specified point in time.
-
E.
underDangerList
Indicates that an entity is classified as being on a designated danger or endangered list, signifying it is at risk or under threat.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61524d22881909284d4aa8db7ebdd |
completed | May 2, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:07 a.m.