Triple
T5850678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinkham Notch |
E130020
|
entity |
| Predicate | hasParkingFor |
P67493
|
FINISHED |
| Object | hikers |
—
|
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: hikers | Statement: [Pinkham Notch, hasParkingFor, hikers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParkingFor Context triple: [Pinkham Notch, hasParkingFor, hikers]
-
A.
hasParking
Indicates that a place or facility provides designated parking space(s) available for use.
-
B.
hasParkingNearby
Indicates that a location has one or more parking facilities or spaces available within a close surrounding area.
-
C.
hasParkStatus
Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
-
D.
hasParkingLotOwner
Indicates that a parking lot is owned or possessed by a specific owner.
-
E.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
- F. None of above. chosen
Provenance (4 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c044a9c4f0819081b8c196932883f6 |
completed | March 22, 2026, 7:36 p.m. |
Created at: March 22, 2026, 3:55 p.m.