Triple
T38582865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frozen Sea |
E932283
|
entity |
| Predicate | travelHazard |
P115167
|
FINISHED |
| Object | dangerous for ships |
—
|
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: dangerous for ships | Statement: [Frozen Sea, travelHazard, dangerous for ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelHazard Context triple: [Frozen Sea, travelHazard, dangerous for ships]
-
A.
travelHazards
chosen
Indicates that there are potential dangers, risks, or obstacles associated with traveling in a particular context or along a specific route.
-
B.
travelAdvisory
Indicates that one authority issues guidance or warnings to others about safety, risks, or conditions related to traveling to a particular place.
-
C.
hazardEncountered
Indicates that an entity has come into contact with or been exposed to a potentially dangerous or harmful condition, object, or situation.
-
D.
hazardEvent
Indicates an occurrence of a dangerous or harmful event that poses a risk or threat within a given context.
-
E.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:32 p.m.