Triple
T28969537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Bufadora |
E734231
|
entity |
| Predicate | hasBestViewingConditions |
P42052
|
FINISHED |
| Object | during strong ocean swells |
—
|
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: during strong ocean swells | Statement: [La Bufadora, hasBestViewingConditions, during strong ocean swells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBestViewingConditions Context triple: [La Bufadora, hasBestViewingConditions, during strong ocean swells]
-
A.
hasViewingConditions
chosen
Indicates that one entity is associated with specific viewing conditions under which it is meant to be observed or evaluated.
-
B.
hasNightViewSpot
Indicates that a location offers a suitable vantage point for viewing the scenery or cityscape at night.
-
C.
hasSunsetPhenomenon
Indicates that a location or context exhibits a notable or characteristic sunset-related visual or atmospheric phenomenon.
-
D.
isVisibleBestIn
Indicates that an entity is considered the most visible or prominent within a specified context or set.
-
E.
hasSunsetView
Indicates that one entity offers a clear or notable view of the sunset from its location or perspective.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 9:04 a.m.