Triple
T12955897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa Cristal |
E310008
|
entity |
| Predicate | hasVisitorRegulation |
P34675
|
FINISHED |
| Object | daily visitor limit |
—
|
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: daily visitor limit | Statement: [Playa Cristal, hasVisitorRegulation, daily visitor limit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorRegulation Context triple: [Playa Cristal, hasVisitorRegulation, daily visitor limit]
-
A.
hasVisitorPolicy
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
-
B.
hasRegulations
chosen
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
C.
hasTourismRestriction
Indicates that there is a limitation, prohibition, or special condition affecting tourism-related activities or access in relation to the referenced entity.
-
D.
canVisit
Indicates that one entity is permitted or able to go to or access another entity or location.
-
E.
visitorRequirement
Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:44 p.m.