Triple
T14379110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pampelonne Beach |
E356553
|
entity |
| Predicate | hasBeachClubType |
P113811
|
FINISHED |
| Object | private beach clubs |
—
|
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: private beach clubs | Statement: [Pampelonne Beach, hasBeachClubType, private beach clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeachClubType Context triple: [Pampelonne Beach, hasBeachClubType, private beach clubs]
-
A.
hasBeachServices
Indicates that an entity provides services or amenities specifically for beach use or beachgoers.
-
B.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as a beach.
-
C.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
D.
hasBeachTagRequirement
Indicates that something is subject to a specific requirement or condition related to beach access, use, or tagging.
-
E.
hasBeachNearby
Indicates that one location is situated close enough to another location to have convenient access to a beach.
- F. None of above. chosen
Provenance (4 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900a67e08190ab1dcf36e6bb3405 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:16 a.m.