Triple
T10188750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Issaquah Alps trail system |
E237977
|
entity |
| Predicate | isUrbanProximityTrails |
P44123
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Issaquah Alps trail system, isUrbanProximityTrails, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanProximityTrails Context triple: [Issaquah Alps trail system, isUrbanProximityTrails, true]
-
A.
isUrbanRoute
Indicates that a route is located within, passes through, or primarily serves an urban or metropolitan area.
-
B.
hasUrbanProximity
chosen
Indicates that one entity is located near or within easy access to an urban area associated with another entity.
-
C.
isRailTrail
Indicates that a path or route is a rail trail, meaning it follows or repurposes a former or existing railway corridor for recreational or transportation use.
-
D.
isUrbanParkAdjacent
Indicates that an urban park is directly next to or shares a boundary with another specified area or feature.
-
E.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded7c3278819093312665b54d888c |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.