Triple
T26301365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teide |
E661566
|
entity |
| Predicate | summitAccessRestriction |
P9584
|
FINISHED |
| Object | permit required |
—
|
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: permit required | Statement: [Teide, summitAccessRestriction, permit required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitAccessRestriction Context triple: [Teide, summitAccessRestriction, permit required]
-
A.
accessRestriction
chosen
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
B.
summitAccessInfrastructure
Indicates the presence or provision of infrastructure that enables access to a summit, such as paths, roads, or transport facilities.
-
C.
accessRestrictedTo
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
-
D.
controlsAccessBetween
Indicates that one entity regulates, manages, or restricts the ability of another entity to interact or communicate with a third entity or resource.
-
E.
hasSummitAccess
Indicates that an entity is permitted or able to reach or enter the summit or highest level of a specified place, system, or structure.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eb2b658819086b8ad443c0a9275 |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:16 p.m.