Triple
T25527064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Camp Road area |
E639802
|
entity |
| Predicate | hasTrailUseRules |
P68232
|
FINISHED |
| Object | multi-use trails for hikers and bikers |
—
|
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 for hikers and bikers | Statement: [Gold Camp Road area, hasTrailUseRules, multi-use trails for hikers and bikers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailUseRules Context triple: [Gold Camp Road area, hasTrailUseRules, multi-use trails for hikers and bikers]
-
A.
hasTrailUseRule
Indicates that a specified rule governs how a particular trail may be used.
-
B.
hasTrailFeature
Indicates that a trail possesses or is characterized by a specific feature or attribute.
-
C.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
D.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
E.
trailUsePolicy
chosen
Indicates the rules or guidelines governing how a trail may be accessed and used.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 3:11 p.m.