Triple
T3403378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadbeach |
E71709
|
entity |
| Predicate | coastalEnvironment |
P35656
|
FINISHED |
| Object | surf beach |
—
|
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: surf beach | Statement: [Broadbeach, coastalEnvironment, surf beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalEnvironment Context triple: [Broadbeach, coastalEnvironment, surf beach]
-
A.
hasCoastalEnvironment
chosen
Indicates that an entity is located in, adjacent to, or characterized by a coastal environment or shoreline setting.
-
B.
coastalInteraction
Indicates an interaction or relationship occurring between entities and a coastal environment, such as along shorelines or near the sea.
-
C.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic area.
-
D.
coastalProtection
Indicates measures or actions taken to preserve, defend, or stabilize coastal areas against erosion, flooding, or other marine-related impacts.
-
E.
flowsAlongCoastOf
Indicates that something, typically a body of water or current, moves in a path that follows and runs adjacent to a coastline.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8e78ec8819089417666dc29f412 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.