Triple
T27282574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa de las Vistas |
E688378
|
entity |
| Predicate | hasBreakwaters |
P34503
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Playa de las Vistas, hasBreakwaters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreakwaters Context triple: [Playa de las Vistas, hasBreakwaters, yes]
-
A.
hasBreakwater
chosen
Indicates that a structure or location is equipped with or associated with a breakwater that provides protection from waves or erosion.
-
B.
hasShelteredWaters
Indicates that one location provides protected or calm waters for another location or activity, shielding it from rough or open conditions.
-
C.
hasCutwaters
Indicates that a structure, typically a bridge pier or similar element, is equipped with cutwaters designed to deflect water flow and reduce hydraulic pressure.
-
D.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
E.
hasMarinaOrStaithe
Indicates that a place includes or is associated with a marina or staithe (a landing stage or mooring area for boats).
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 11:08 a.m.