Triple
T21538876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynmouth Sands rocks |
E531423
|
entity |
| Predicate | navigationWarning |
P26839
|
FINISHED |
| Object | reefs and rocks awash |
—
|
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: reefs and rocks awash | Statement: [Lynmouth Sands rocks, navigationWarning, reefs and rocks awash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationWarning Context triple: [Lynmouth Sands rocks, navigationWarning, reefs and rocks awash]
-
A.
navigationProblemAddressed
Indicates that a navigation-related issue, obstacle, or challenge has been identified and dealt with or resolved.
-
B.
navigationRegulation
Indicates rules or constraints that govern how navigation or movement is allowed, restricted, or managed within a particular space or system.
-
C.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
D.
navigationNote
chosen
Indicates that there is an auxiliary note or instruction intended to guide or assist navigation within a resource, interface, or environment.
-
E.
navigationOutput
Indicates that an entity produces or provides navigational information or guidance as an output to another entity or system.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d10a2888190bc4e502a829c76a4 |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.