Triple
T27255879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dog Rocks |
E687611
|
entity |
| Predicate | isHazardToNavigation |
P22896
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dog Rocks, isHazardToNavigation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHazardToNavigation Context triple: [Dog Rocks, isHazardToNavigation, true]
-
A.
hasNavigationHazardRelevance
Indicates that something is relevant to, affected by, or poses a potential hazard to navigation.
-
B.
isNavigationalAid
Indicates that one entity serves as a navigational aid or guide to help locate, orient, or move toward another entity or destination.
-
C.
hasNavigationHazard
chosen
Indicates that something presents or contains a condition, object, or feature that poses a risk or obstacle to safe navigation.
-
D.
maritimeHazard
Indicates a condition, object, or situation at sea that poses a risk to vessels, navigation, or maritime operations.
-
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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626b9862c819084ddb3eb47678bcb |
completed | May 2, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:49 a.m.