Triple
T4876685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caswell Bay |
E109221
|
entity |
| Predicate | hasSurfBreakType |
P22583
|
FINISHED |
| Object | beach break |
—
|
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: beach break | Statement: [Caswell Bay, hasSurfBreakType, beach break]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfBreakType Context triple: [Caswell Bay, hasSurfBreakType, beach break]
-
A.
hasSurfBreak
chosen
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
B.
hasBreakwater
Indicates that a structure or location is equipped with or associated with a breakwater that provides protection from waves or erosion.
-
C.
beachSectorSupported
Indicates that a particular beach sector is maintained, serviced, or otherwise operationally supported by a responsible party or system.
-
D.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as a beach.
-
E.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.