Triple
T7456047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foveaux Strait |
E172124
|
entity |
| Predicate | isHazardousFor |
P63246
|
FINISHED |
| Object | small vessels |
—
|
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: small vessels | Statement: [Foveaux Strait, isHazardousFor, small vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHazardousFor Context triple: [Foveaux Strait, isHazardousFor, small vessels]
-
A.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
B.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
C.
hasObjectiveHazards
chosen
Indicates that an entity is associated with concrete, externally verifiable dangers or risks.
-
D.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
E.
dangerousWhen
Indicates that one entity becomes harmful, risky, or unsafe under the conditions or in the presence of another entity or situation.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3af58dc819093fb0482482779a3 |
completed | March 27, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:15 p.m.