Triple
T8298706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurel Ridge State Park |
E194289
|
entity |
| Predicate | trailSystemType |
P51754
|
FINISHED |
| Object | long-distance hiking trail corridor |
—
|
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: long-distance hiking trail corridor | Statement: [Laurel Ridge State Park, trailSystemType, long-distance hiking trail corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailSystemType Context triple: [Laurel Ridge State Park, trailSystemType, long-distance hiking trail corridor]
-
A.
trailNetworkType
chosen
Indicates the classification of a trail within a broader trail network, such as its role, category, or type of route in that system.
-
B.
trailSystemLength
Indicates the total measured length of a trail system associated with an entity.
-
C.
beltwayType
Indicates the specific classification or type of a beltway (ring road) associated with a given roadway or area.
-
D.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
E.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7dfb60e48190bfa5de1c1496d3b5 |
completed | March 31, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.