Triple
T6844578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer Park (Mercer Island) |
E157859
|
entity |
| Predicate | hasTypeOfTrails |
P2401
|
FINISHED |
| Object | multi-use trails |
—
|
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: multi-use trails | Statement: [Pioneer Park (Mercer Island), hasTypeOfTrails, multi-use trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfTrails Context triple: [Pioneer Park (Mercer Island), hasTypeOfTrails, multi-use trails]
-
A.
hasTrailType
chosen
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
B.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
C.
hasRailTrail
Indicates that one location or entity possesses, includes, or is connected by a rail trail (a recreational trail converted from or running along a former or existing railway corridor) to another location or entity.
-
D.
hasNearbyTrailType
Indicates that one entity has another entity of a specified trail type located in close proximity to it.
-
E.
hasTrailheads
Indicates that one location or area contains or provides access points where trails begin.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b8627081908e34d2b942d08aef |
completed | March 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.