Triple
T32826147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puente de Dios |
E839559
|
entity |
| Predicate | requiresWalk |
P163672
|
FINISHED |
| Object | short hike from parking area |
—
|
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: short hike from parking area | Statement: [Puente de Dios, requiresWalk, short hike from parking area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresWalk Context triple: [Puente de Dios, requiresWalk, short hike from parking area]
-
A.
requiresJourneyOf
chosen
Indicates that one entity can only be achieved, accessed, or completed by undertaking a journey or progression involving another entity.
-
B.
requiresFromHikers
Indicates that something imposes a condition, obligation, or necessity specifically on hikers.
-
C.
requiresFinding
Indicates that one entity’s validity, execution, or completion is contingent upon a specific finding or determination being made about another entity.
-
D.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
E.
walkInPolicy
Indicates that an entity allows or operates under a policy where individuals can arrive and be served without a prior appointment.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 1, 2026, 1:15 a.m.