Triple
T38208286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Dot Trail |
E1009264
|
entity |
| Predicate | parkingRequired |
P41508
|
FINISHED |
| Object | Monadnock State Park parking fee |
—
|
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: Monadnock State Park parking fee | Statement: [White Dot Trail, parkingRequired, Monadnock State Park parking fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkingRequired Context triple: [White Dot Trail, parkingRequired, Monadnock State Park parking fee]
-
A.
parkingRequirement
chosen
Indicates the specified conditions or obligations related to providing or using parking associated with an entity or activity.
-
B.
parkShuttleRequired
Indicates that using a shuttle service is necessary to access or move within a particular park or parking area.
-
C.
hasParking
Indicates that a place or facility provides designated parking space(s) available for use.
-
D.
hasParkingFor
Indicates that a place or facility provides designated parking spaces suitable for a specified type of vehicle or user.
-
E.
parkingType
Indicates the specific kind or category of parking arrangement associated with an entity (e.g., street, garage, lot, reserved).
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.