Triple
T15278841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatamá National Natural Park |
E365212
|
entity |
| Predicate | hasLimitedTourism |
P53204
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tatamá National Natural Park, hasLimitedTourism, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedTourism Context triple: [Tatamá National Natural Park, hasLimitedTourism, yes]
-
A.
hasTourismRestriction
chosen
Indicates that there is a limitation, prohibition, or special condition affecting tourism-related activities or access in relation to the referenced entity.
-
B.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
C.
hasTourismPotential
Indicates that a place or resource possesses qualities that make it attractive or suitable for tourism activities or development.
-
D.
hasTourismImpactOn
Indicates that one entity affects or influences the tourism levels, patterns, or attractiveness of another entity.
-
E.
hasTourismAuthority
Indicates that an entity holds official responsibility or power to manage, regulate, or oversee tourism-related activities for another entity or area.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e504d8c8190ad6c565a31d1a9bd |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.