Triple
T12955965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaino sector |
E310010
|
entity |
| Predicate | hasAccessPointTo |
P93497
|
FINISHED |
| Object | Tayrona National Natural Park trail network |
—
|
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: Tayrona National Natural Park trail network | Statement: [Zaino sector, hasAccessPointTo, Tayrona National Natural Park trail network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessPointTo Context triple: [Zaino sector, hasAccessPointTo, Tayrona National Natural Park trail network]
-
A.
hasAccessPointFrom
Indicates that an entity can be reached or entered from a specific access point.
-
B.
hasTrailAccessPoint
chosen
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
-
C.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
D.
isMajorAccessPointFor
Indicates that something serves as a primary or significant entry or connection point for accessing another entity or system.
-
E.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
- 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.