Triple
T35363203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liard River Hot Springs |
E1021550
|
entity |
| Predicate | hasCampingReservationSystem |
P200527
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Liard River Hot Springs, hasCampingReservationSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampingReservationSystem Context triple: [Liard River Hot Springs, hasCampingReservationSystem, yes]
-
A.
hasCampingReservations
Indicates that an entity has booked or secured one or more reservations for camping.
-
B.
hasCampingOption
Indicates that an entity offers or includes the possibility to camp (e.g., designated camping facilities or areas).
-
C.
hasCampingPolicy
Indicates that an entity specifies rules, restrictions, or guidelines regarding camping activities on its premises or within its jurisdiction.
-
D.
hasCampground
Indicates that one entity provides, contains, or is associated with a campground facility or area for another entity.
-
E.
hasCampingAmenity
Indicates that a place or facility provides a specific camping-related amenity or feature.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
| PDg | Predicate description generation | batch_69ff935f48808190aa6f4834f59d45b8 |
completed | May 9, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.