Triple
T6907426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabo das Tormentas |
E159844
|
entity |
| Predicate | maritimeHazard |
P74048
|
FINISHED |
| Object | storms |
—
|
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: storms | Statement: [Cabo das Tormentas, maritimeHazard, storms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeHazard Context triple: [Cabo das Tormentas, maritimeHazard, storms]
-
A.
maritimeActivity
Indicates activities, operations, or behaviors that take place at sea or are directly related to maritime environments and navigation.
-
B.
maritimeDomain
Indicates a relationship or activity that occurs within, affects, or is specifically associated with the maritime domain (seas, oceans, and related maritime operations).
-
C.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
D.
maritimeUsage
Indicates the extent to which something is used for or involved in maritime activities, such as sea transport, navigation, or ocean-related operations.
-
E.
marineArea
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
- F. None of above. chosen
Provenance (4 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9bd7b3c8190842eb83679c322d5 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:25 p.m.