Triple
T37838379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mowich Lake Campground |
E943399
|
entity |
| Predicate | hasVehiclePolicy |
P30753
|
FINISHED |
| Object | no car camping at sites |
—
|
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: no car camping at sites | Statement: [Mowich Lake Campground, hasVehiclePolicy, no car camping at sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVehiclePolicy Context triple: [Mowich Lake Campground, hasVehiclePolicy, no car camping at sites]
-
A.
vehiclePolicy
chosen
Indicates a relationship where a policy governs, regulates, or defines rules and conditions for the use, operation, or management of a vehicle.
-
B.
hasVehicle
Indicates that one entity possesses, owns, or is assigned a vehicle.
-
C.
hasInsurancePolicyOnVictim
Indicates that an entity holds an insurance policy that covers or is taken out on the victim.
-
D.
hasNotableVehicleAssociated
Indicates that an entity is associated with a specific vehicle that is considered notable or significant in some recognized context.
-
E.
isOnPolicy
Indicates that an action, configuration, or behavior complies with and adheres to a specified policy or set of rules.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.