Triple
T17989617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worms Head |
E430331
|
entity |
| Predicate | safetyGuidance |
P97924
|
FINISHED |
| Object | visitors advised to check tide times |
—
|
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: visitors advised to check tide times | Statement: [Worms Head, safetyGuidance, visitors advised to check tide times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyGuidance Context triple: [Worms Head, safetyGuidance, visitors advised to check tide times]
-
A.
safetyAdvice
chosen
Indicates that one entity provides guidance or recommendations to another entity about how to avoid danger or reduce risk in a particular context.
-
B.
safetyCategory
Indicates the classification of something according to its level or type of safety.
-
C.
safetyResponse
Indicates how an entity reacts or what measures it takes in response to a potential or actual safety-related situation.
-
D.
safetyContext
Indicates the circumstances, conditions, or environment that affect how safe an action, object, or situation is.
-
E.
safetyRationale
Indicates the reasoning or justification provided to explain how and why something is considered safe or made safe.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29e47a88190be58b79c73d3e652 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.