Triple
T32074623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crothers Woods |
E819108
|
entity |
| Predicate | trailUseRegulation |
P68232
|
FINISHED |
| Object | multi-use shared 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 shared trails | Statement: [Crothers Woods, trailUseRegulation, multi-use shared trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailUseRegulation Context triple: [Crothers Woods, trailUseRegulation, multi-use shared trails]
-
A.
trailUsePolicy
chosen
Indicates the rules or guidelines governing how a trail may be accessed and used.
-
B.
navigationRegulation
Indicates rules or constraints that govern how navigation or movement is allowed, restricted, or managed within a particular space or system.
-
C.
trailUses
Indicates that a trail supports or is designated for specific types of use or activities (such as hiking, biking, or horseback riding).
-
D.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
E.
technicalRegulationsAuthority
Indicates that an authority is responsible for establishing, implementing, or overseeing technical regulations governing certain activities, products, or services.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b52ac6f48190ac3e563e45464d43 |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:23 a.m.