Triple
T32551362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnstown Inclined Plane |
E831979
|
entity |
| Predicate | touristViews |
P99257
|
FINISHED |
| Object | Conemaugh River valley |
—
|
NE NERFINISHED |
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: Conemaugh River valley | Statement: [Johnstown Inclined Plane, touristViews, Conemaugh River valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristViews Context triple: [Johnstown Inclined Plane, touristViews, Conemaugh River valley]
-
A.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
B.
typicalSights
chosen
Indicates that certain sights or visual features are commonly or characteristically observed in association with a given entity or context.
-
C.
touristAccess
Indicates that a place or resource is available for use or visitation by tourists.
-
D.
sights
Indicates that one entity perceives or observes another entity or object using vision.
-
E.
tourismImage
Indicates a relationship where something serves as a visual representation or promotional image associated with tourism for a place, attraction, or destination.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:02 a.m.