Triple

T262768
Position Surface form Disambiguated ID Type / Status
Subject Lynn Woods Reservation E5572 entity
Predicate hasTrailSystem P3625 FINISHED
Object extensive network of hiking 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: extensive network of hiking trails | Statement: [Lynn Woods Reservation, hasTrailSystem, extensive network of hiking trails]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTrailSystem
Context triple: [Lynn Woods Reservation, hasTrailSystem, extensive network of hiking trails]
  • A. hasTrail chosen
    Indicates that an entity possesses, includes, or is associated with a trail or pathway.
  • B. hasTrailType
    Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
  • 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. hasTransportationSystem
    Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
  • E. hasRailSystem
    Indicates that an entity possesses or is served by a rail-based transportation system.
  • 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_69a2580a64ac8190ad76e34bb0715b5e completed Feb. 28, 2026, 2:50 a.m.
NER Named-entity recognition batch_69a25d8c7f448190af9145256f994177 completed Feb. 28, 2026, 3:14 a.m.
PD Predicate disambiguation batch_69a25b6e07748190834022a65ba6d803 completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:55 a.m.