Triple
T8081359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa de las Conchas |
E188621
|
entity |
| Predicate | nudismPolicy |
P80386
|
FINISHED |
| Object | tolerated in practice |
—
|
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: tolerated in practice | Statement: [Playa de las Conchas, nudismPolicy, tolerated in practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nudismPolicy Context triple: [Playa de las Conchas, nudismPolicy, tolerated in practice]
-
A.
hasNSFWPolicy
Indicates that an entity has an established policy governing the handling, display, or treatment of not-safe-for-work (NSFW) content.
-
B.
accommodationPolicy
Indicates the rules or guidelines that govern how accommodations are provided, used, or managed in a given context.
-
C.
boardingPolicy
Indicates the rules or procedures governing how and in what order passengers are allowed to board a vehicle or vessel.
-
D.
hasCampingPolicy
Indicates that an entity specifies rules, restrictions, or guidelines regarding camping activities on its premises or within its jurisdiction.
-
E.
venuePolicy
Indicates the rules or guidelines that govern how activities or events may be conducted at a particular venue.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a699388190a5b8e26524ae43e5 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:28 p.m.