Triple
T24563553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anse Cocos |
E607721
|
entity |
| Predicate | hasAccessRouteType |
P13326
|
FINISHED |
| Object | forest trail |
—
|
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: forest trail | Statement: [Anse Cocos, hasAccessRouteType, forest trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessRouteType Context triple: [Anse Cocos, hasAccessRouteType, forest trail]
-
A.
hasAccessRouteTo
Indicates that one entity possesses a path, connection, or means of reaching or interacting with another entity.
-
B.
hasRouteType
chosen
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
C.
hasAccessBy
Indicates that one entity is permitted to access, use, or interact with another entity, typically under specified permissions or conditions.
-
D.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
-
E.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f8a7488190a11f32014539a4a3 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.