Triple
T32288840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taghazout Beach |
E824907
|
entity |
| Predicate | nearbySurfSpot |
P22583
|
FINISHED |
| Object | Anchor Point |
—
|
NE NERFINISHED |
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: Anchor Point | Statement: [Taghazout Beach, nearbySurfSpot, Anchor Point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbySurfSpot Context triple: [Taghazout Beach, nearbySurfSpot, Anchor Point]
-
A.
nearestMajorBeach
Indicates the relationship where a location is associated with the closest significant or well-known beach to it.
-
B.
hasSurfBreak
chosen
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
C.
discoveredAsSurfSpotBy
Indicates that a location became recognized and used as a surf spot through the actions or discovery of a particular person or group.
-
D.
nearbyOceanicEntryPoint
Indicates that one location serves as an ocean access point (such as a harbor, beach, or port) situated close to another specified place.
-
E.
hasBeachNearby
Indicates that one location is situated close enough to another location to have convenient access to a beach.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 12:44 a.m.