Triple
T1124799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Killbear Provincial Park |
E24694
|
entity |
| Predicate | hasCampingFacility |
P17960
|
FINISHED |
| Object | electrical campsites |
—
|
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: electrical campsites | Statement: [Killbear Provincial Park, hasCampingFacility, electrical campsites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampingFacility Context triple: [Killbear Provincial Park, hasCampingFacility, electrical campsites]
-
A.
hasCampground
Indicates that one entity provides, contains, or is associated with a campground facility or area for another entity.
-
B.
trainingCampSite
Indicates that a location serves as the site where training camps are held or conducted.
-
C.
hasCabins
Indicates that an entity possesses or includes one or more cabins as part of its structure or facilities.
-
D.
hasMountainHut
Indicates that one entity possesses, contains, or is associated with a mountain hut located within its area or domain.
-
E.
hasAccommodation
chosen
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4749ac8190b0fbddac2e9b2586 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.